Code review can be better
Slightly unusual genre today: a negative result about our git-review tool for a different take on code review process, which we decided to shelve, at least for the time being.
The financial transactions database to power the next 30 years of Online Transaction Processing.
Visit tigerbeetle.com → On Hacker News Oct 2022 – Feb 2026
Software Engineering 9Systems & Performance 7Databases & Data 3Tech Industry & Business 2Startups 1Open Source 1
Slightly unusual genre today: a negative result about our git-review tool for a different take on code review process, which we decided to shelve, at least for the time being.
“640K ought to be enough for anybody.” - Supposedly Bill Gates, circa 1981.
TigerBeetle is a distributed financial transactions database, designed for mission critical safety. How do you test something so critical? Well, we could tell you (and we will), but why not show you?
A textbook database problem
Synadia and TigerBeetle have together pledged $512,000 to the Zig Software Foundation over the next two years in support of the language, leadership, and communities building the future of simpler systems software.
Wherein we make progress towards solving one of the most vexing problems of Computer Science — naming things.
A popular data-oriented design pattern is a Struct of Arrays. Is an Array of Enums also useful? Yes! But let’s do a refresher on struct of arrays (SoA) first:
I have a super power. I want to share it in this blog post so that you, my dear reader, also have it!
Consider this tale of I/O and performance. We’ll start with blocking I/O, explore io_uring and kqueue, and take home an event loop very similar to some software you may find familiar.
TigerBeetle is a financial transactions database built for correctness. Yet, building a correct system from correct components remains a challenge:
In July 2020, I stumbled into a fundamental limitation in the general-purpose database design for transaction processing.