Readable accounts
Name accounts after what they are, like rider:123:wallet or platform:fees, and read many at
once with patterns like rider:123:*.
One 8-core AWS machine, a simulated brokerage, each system at its best. Closed loop: clients send requests back to back, so this is the most each system can do. We wrote the benchmark, so read the full results and caveats.
Readable accounts
Name accounts after what they are, like rider:123:wallet or platform:fees, and read many at
once with patterns like rider:123:*.
Safe to retry
Every posting carries your own id. Send it twice and it is applied once.
All or nothing
Group postings into a chain, and either every one of them happens or none do.
Fast under contention
Balances live in TigerBeetle, so busy accounts don’t make writes queue behind locks.