The 1000x faster financial database
from Changelog Interviews
In July of 2020, Joran Dirk Greef stumbled into a fundamental limitation in the general-purpose database design for transaction processing. This sent him on a path that ended with TigerBeetle, a redesigned distributed database for financial transactions that yielded three orders of magnitude faster OLTP performance over the usual (general-purpose) suspects. On this episode, Joran joins Jerod to explain how TigerBeetle got so fast, to defend its resilience and durability claims as a new market entrant, and to stake his claim at the intersection of open source and business. Oh, plus the age old question: Why Zig?
Embed this episode
Chapters
- 0:00 Welcome to The Changelog
- 1:25 Sponsor: Augment Code
- 4:33 Start the show!
- 5:18 Stumbling into it
- 8:27 Maybe I did it wrong
- 9:41 It's the row locks
- 11:33 Pareto meets the Mag 7
- 13:40 Financial, not SQL, transactions
- 14:51 A specialized database
- 18:01 Why build yet another database?
- 22:56 Sponsor: Depot
- 25:16 Where do you start?
- 27:46 Who is 'we'?
- 29:09 10_000x faster?!
- 30:44 New world, new constraints
- 32:14 Row, column, mulit-major
- 36:08 Multi-row major implications
- 41:45 Embarrassingly simple
- 44:36 On durability
- 55:05 Centuries of testing
- 57:17 What about real-world use tho
- 1:02:38 Worst-case scenario logic
- 1:03:55 Sponsor: Notion
- 1:07:03 TigerBeetle Simulator
- 1:15:38 The open source story
- 1:25:56 Jerod reacts
- 1:26:18 What about AWS re-hosting
- 1:30:57 Written in Zig
- 1:36:28 Redis open source again?
- 1:37:28 Wrapping up
- 1:38:10 Closing thoughts
No transcript yet.