Skip to content
0:00 / 0:00

#tigerbeetle#zig#database

The FASTEST and SAFEST Database

The PrimeTime

1.1M subscribers • 18 videos on Hallway

YouTube
  • Recommended by 2 people: 2 in engineering communities.
  • Presented by The Primeagen

Intermediate. Assumes working knowledge.

322K views2 years ago2 recommendations

Databases and dataSystems programmingZigDatabase internalsTesting

The Primeagen reacts to and explains the design, performance, and rigorous testing philosophy of the TigerBeetle financial database.

Recorded live on twitch, GET IN twitch.tv/ThePrimeagen Become a backend engineer. Its my favorite site boot.dev/?promo=PRIMEYT This is also the best way to support me is to support yourself becoming a better backend engineer. MY MAIN YT CHANNEL: Has well edited engineering videos youtube.com/ThePrimeagen Discord discord.gg/ThePrimeagen Have something for me to read or react to?: reddit.com/r/ThePrimeagenReact/ Kinesis Advantage 360: bit.ly/Prime-Kinesis Hey I am sponsored by Turso, an edge database. I think they are pretty neet. Give them a try for free and if you want you can get a decent amount off (the free tier is the best (better than planetscale or any other)) turso.tech/deeznuts

Why it's here

2 people recommend this

What people say. Recommended for its engaging breakdown of TigerBeetle's unique architecture, safety guarantees, and testing practices in Zig.

u/bonkyandthebeatmanin r/Zig • Recommends

On “Do you guys really put your test code inside your regular code?”

>what I usually do is to have a bunch of test scenarios for the production code and code is feed and the result should be the same my man, this is literally a test. This is what unit tests are... are we not on the same page here? >I have never seen any one with a solution that works well for threaded code. I just gave you one... tigerbeetle. here is a really good presentation on what the philosophy is. Not only is it multithreaded, it's *distributed.* meaning it's literally running across many different physical machines.

u/asdoduidaiin r/sre • Recommends

On “How do you make “production readiness” observable before the incident?”

…omplete understanding of the states coming from concurrent algorithms and nodes/layers interactions. Two examples of that - the intent of having awareness of all app states, and careful choices based on the knowledge of every detail - I think is: \- https://techpreneurr.medium.com/why-whatsapp-chose-erlang-and-never-looked-back-353248e2d6c7 \- [video So about prioritisation, if you know the app states, and you choose based on careful detailed evaluation, you have it at least 80% covered. Then, you still have to check the running of it, the load testing, the failure injection, chaos engineering, and also about storage/DB: Jepsen/Formal testing, to make sure that the claims of the most…