TigerStyle! (Or How To Design Safer Systems in Less Time) by Joran Dirk Greef
Channel:TigerBeetle · Length:1:01:59 · Published:2023-04-26 · Views:88422
Summary
Joran Dirk Greef's Systems Distributed '23 talk on TigerStyle, the engineering methodology behind TigerBeetle. It covers designing safer systems in less time through up-front design, assertions, and deterministic simulation.
Why HN recommends it
HN commenters, including TigerBeetle people, recommend it as the explanation of a methodology for building defect-free, high-assurance software.
The TigerStyle video is well worth watching for anyone who wants to build defect-free software systems — HN, 2024
Software architecture & design · Testing, debugging & developer tools · Databases & storage
Subtitles (excerpt)
foreign [Music] [Music] [Music] so I want to teach you a magic trick to think of the most difficult distributed systems problem or Advanced software project you can imagine uh perhaps it's a consensus protocol a database or an operating system these are just my examples I think you will think of like self-driving cars or some medical device something like that and then so picture this and then you build it successfully in a fraction of the time so if it took 10 years before to build then with this trick you do it in four or five so you still work hard but with more velocity so the result is better safer faster simpler to operate and you sleep well at night because by the time you're done it's the most Rock Solid system you've ever built at least this has been my own experience being lucky to learn this trick or the style of development from people like Gerard Holtzman and James culling and to put it into practice in the creation of tiger beetle less than three years ago so tiger beetle is a distributed Financial Accounting database it's been designed for Mission critical safety and performance and the way that we develop tiger beetle is something that gets our team excited because when you see these systems run the way
On Hacker News
I second this recommendation. I'm impressed by what TigerBeetle has accomplished, and would love to see more of the industry approach software engineering with their philosophy and rigour. The TigerStyle video is well worth watching for anyone who wants to build defect-free software systems, or recognizes that this is the correct thing to aim for. [VIDEO] — samatman, 2024-07
Joran from TigerBeetle here! This is a “walking sim” real visualization of our Deterministic Simulation Testing harness, the VOPR. Typically we do DST headless in the terminal but this is a visualization, more or less the same thing but with a gaming engine on top. It’s running real TigerBeetle code, but with simulated network/storage and fault injection, and multiple replicas in a cluster, all c… — jorangreef, 2025-11
You're right! In the past, distributed databases written without Deterministic Simulation Testing (DST) would typically take around ~10 years (~5 years for the consensus protocol and ~5 years for the storage engine). And then not without bugs. However, and we write about this also in the post, but TigerStyle and DST enabled us to ship TigerBeetle to production in 3.5 years, in less time, to a hig… — jorangreef, 2025-10
We apply this pretty much fully at TigerBeetle [1]. Reason being that TigerStyle is not only about shipping safer software, but shipping it in less time [2], factoring in the Total Cost of Ownership to end users. In other words, not only optimizing our development time, but also all the time spent in production with subsequent fixes. [1] [LINK] [2] [VIDEO] — jorangreef, 2025-07
Appreciated your post, Lewis! From the beginning, TigerStyle was intended not only for TigerBeetle as infrastructure, but for software (up and down the stack) in general. Nobody wants buggier, slower software. And so TigerStyle as a methodology was codified primarily to address this problem: How to write “higher quality software in less time”? [1] Before designing TigerBeetle, I was finding the p… — jorangreef, 2025-07
Related videos
- ZFS: The Last Word in File Systems Part 1 · Deirdré Straughan · 1:01:26
- Modeling Data Concurrency w/ Asynchronous I/O in Zig - RedisConf 2020 · Redis · 49:19
- Writing a Wayland Compositor in Zig - Isaac Freund · Zig SHOWTIME · 42:19
- A New Way to look at Networking · GoogleTalksArchive · 1:21:15
- RailsConf 2014 - All the Little Things by Sandi Metz · Confreaks · 38:47
- "Simple Made Easy" - Rich Hickey (2011) · Strange Loop Conference · 1:01:38
- "Making Impossible States Impossible" by Richard Feldman · elm-conf · 25:06
- "Testing Distributed Systems w/ Deterministic Simulation" by Will Wilson · Strange Loop Conference · 40:20
- 🚀 TDD, Where Did It All Go Wrong (Ian Cooper) · DevTernity Conference · 1:03:55
- Bret Victor - Inventing on Principle · Rui Oliveira · 54:20
- How To Design A Good API and Why it Matters · Google TechTalks · 1:00:19
- The Value of Values with Rich Hickey · InfoQ · 31:43
- Overwatch Gameplay Architecture and Netcode · GDC Festival of Gaming · 1:04:03
- Solving Problems the Clojure Way - Rafal Dittwald · Clojure/north · 1:02:26
- Lecture 1A: Overview and Introduction to Lisp · MIT OpenCourseWare · 1:12:55
- Debugging Under Fire: Keep your Head when Systems have Lost their Mind • Bryan Cantrill • GOTO 2017 · GOTO Conferences · 52:34