TigerBeetle
No written verdict yet. Here is what commenters said.
Why people recommend it
“You can go the TigerBeetle route”
“maybe you'd believe TigerBeetle which is also single threaded by design”
Show 3 more
“perhaps you'd believe the TigerBeetle team who also made their database single threaded by design”
“Can't wait to see this.”
“Their simulation is fantastic”
Caveats and dissent
“putting their super duper high reliability database on top of it”
“the drop in non-batch performance was disappointing”
Often compared with
Who recommends it in their own words
From the makers not counted in the ranking
“We have six replicas, and under normal operation we only need acknowledgements from three”
“if you take a look at our LSM compaction, regardless of the table size, we compact at the 512 KiB block granularity”
“Empirically, they just haven't been a problem for TigerBeetle.”
“We also reached production in 3.5 years”
“I've worked on two”
“We have two state machines, an accounting one, and a simple echo one here”
Threads where it came up
- Building a high-performance ticketing system with TigerBeetle 8 mentions
- TigerBeetle Core System Architecture: Deconstructing Performance Engineering 5 mentions
- Static Allocation with Zig 5 mentions
- Rewrite Bun in Rust has been merged 4 mentions
- TigerBeetle: A Trillion Transactions [video] 4 mentions
- The JavaScript Midlife Crisis 2 mentions
Data: tigerbeetle.json. Quotes are verbatim; the verdict and theme labels are written by a model from these comments, and every clause links to its sources.
All comments 40
“tigerbeetle much different result”
“You can go the TigerBeetle route”
> I was writing Rhino on the JVM before Node came out because I was absolutely convinced the world would move to server-side JavaScript. > And I think now, I think a lot of the reason why people went into NPM was because the tooling in C was so terrible. > Like, how do you compile a C program? Are some interesting quotes and hint much more to lack of knowledge on server compiled languages than a "performance sketch".
> In the month of July 2020, we developed a prototype of TigerBeetle in Node as a performance sketch to measure the basic components of the design (batching, TCP protocol, cryptographic checksums everywhere, fsync journalling, in-memory business logic and hash table operations). https://github.com/tigerbeetle/tigerbeetle-history-archive/blob/main/docs/HISTORY.md
“Read TigerBeetle's own”
“maybe you'd believe TigerBeetle which is also single threaded by design”
“perhaps you'd believe the TigerBeetle team who also made their database single threaded by design”
“Can't wait to see this.”
“Their simulation is fantastic”
“it is demonstrated how types and assertions work together in TigerBeetle”
“TigerBeetle has static allocation for their known workload.”
It works really well for a ton of use cases (e.g. any data acquisition task, which is mostly what I use C for...)
Some thoughts on this here: https://matklad.github.io/2025/12/23/static-allocation-compilers.html
“One of the preeminent Zig software projects, Tigerbeetle”
“Check out tigerbeetle if you want a good example.”
“come to mind as decently popular projects”
“found only 7 medium/low priority issues”
“I wonder if Tigerbeetle will also have problems arguing for their solution”
“putting their super duper high reliability database on top of it”
“There is also a database written in Zig that seems to be fairly successful”
> how many hundred terabytes of data can you get away with the single beefy server You can have multiple petabytes on a single beefy server with excellent performance characteristics. This is already a thing. The part of the database that doesn't scale with storage density is cache replacement algorithms, as a matter of theory. There are some problems a cache can't solve. These degrade long before you get to petabyte
“We are always a big fan of the tigerbeetle engineering”
“This looks like yet another basic key value store.”
“On the streaming side, are you looking for Change Data Capture?”
“have https://github.com/tigerbeetle/tigerbeetle/blob/main/docs/TIGER_STYLE.md#naming-things bookmarked”
“https://tigerbeetle.com wouldn't have chosen it unless they found it faster than C”
“they are definitely thinking about the problem differently from us”
“I first heard about this while learning about TigerBeetle”
“with a bunch of assertions all other the place to triple check that each block is accounted for”
“Static allocation is a large part of TigerBeetle's something else.”
“TigerStyle is quite a bit more than just static allocation”
“One key thing to understand about TigerBeetle is that it's a file-system-backed database.”
“https://github.com/tigerbeetle/tigerbeetle”
“adding assertions like TigerBeetle does”
“TigerBeetle's support for Zig”
I recommend having instant recognition of all the powers up to 2^24, this has proven very useful over the years e.g. when skimming quickly through a log searching for anomalies, flag patterns etc. If you recite them in sequence twice a day for a couple of weeks, then they’ll stick in your mind for decades. I can say from experience this method also works for the NATO phonetic alphabet, Hamlet’s soliloquies, ASCII, an
“I d recommend reading TigerBeetle's documentation”
“There's an actual production grade database written in zig”
“caused the drop in transaction performance we observed”
“All TigerBeetle's clients also auto batch under the hood”