Skip to content
PodSubs
ShowsPeopleGuestsJobsNewsEvents
More
BlogPodCred
Menu
ShowsPeopleGuestsJobsNewsEventsBlogPodCredNetworksSign in
Join nowSign in
  • Shows
  • People
  • Jobs
  • News
  • More
    • Guests
    • Events
    • Blog
    • PodCred
    • Networks
    Join nowSign in

Developer Voices

Developer Voices artwork

Databases, Ambitions, and a Testing Silver Bullet? (With Joran Dirk Greef)

Oct 4, 20231 hr 7 minAudio

How far would you go to get the kind of database you want? How deep into the stack would you dive to re-architect a system for the kind of performance, reliability and scale you believe in? Today's guest has decided to go all in, as he’s tackling the database problem from the fsync up. In this week’s Developer Voices we talk to Joran Dirk Greef, whose ambitions - combined with the lacklustre performance of his project's payment system - have led him to build a new database called TigerBeetle, that tackles some meaty problems. They’re attempting to build a database that can be durable in the face of fsync-corner cases, highly available in the face of all kinds of hidden network problems, and performant enough to outpace existing financial systems. And on top of all those goals, they’re doing it with an interesting new language you may not have heard of - Zig. What makes him want to take on this big a challenge? What problems keep him awake at night? And what is he doing to turn all that ambition into an achievable launch strategy? Listen on and find out… - TigerBeetle on Twitter: https://twitter.com/TigerBeetleDB TigerBeetle on YouTube: https://www.youtube.com/channel/UC3TlyQ3h6lC_jSWust2leGg Kris on Twitter: https://twitter.com/krisajenkins Kris on LinkedIn: https://www.linkedin.com/in/krisjenkins/ Joran’s QCon ‘23 Talk: https://www.youtube.com/channel/UC3TlyQ3h6lC_jSWust2leGg Viewstamped Replication Revisited (paper): https://pmg.csail.mit.edu/papers/vr-revisited.pdf Github Test Cases for Journal recovery code: https://github.com/tigerbeetle/tigerbeetle/blob/b4dd441502894cbe9d48cb90ff0bc6a12c378591/src/vsr/journal.zig#L1181-L1213MySQL transactions per second vs fsyncs per second: https://sirupsen.com/napkin/problem-10-mysql-transactions-per-second

Audio and video play straight from the show's own hosting. PodSubs stores and serves no media.

Hosts and Guests

Nobody is credited on this episode yet.

Credit the people on this episode

Be the first to rate this episode

More episodes

All episodes
  1. Why Lisp Thrives In The Age Of AI (with Cameron Barré)

    Nov 11, 20261 hr 40 minAudio

    Earlier this year it looked like AI might kill programming language innovation. Coding agents were at their best in the mainstream languages with decades of training data, which made the barrier to adopting anything new...

    Credit the people on this episode

  2. How Would You Type-Check 30 Million Lines of PHP? (with Julien Verlaguet)

    Sep 25, 20262 hr 22 minAudio

    How would you manage 30 million lines of PHP? You can't rewrite it - you'd be fired long before you delivered. That was the problem facing Facebook around 2011, and their answer was to add a type system, giving birth to...

    Credit the people on this episode

  3. DuckDB And The Burden of Success (with Hannes Mühleisen)

    Aug 26, 20261 hr 46 minAudio

    Building something people actually want is supposed to be the happy ending. But it arrives with a bill attached: feature requests you didn't ask for, pull requests you'd rather not maintain forever, users demanding the...

    Credit the people on this episode

  4. The Enterprise AI Gap (with James Brown)

    Aug 12, 20261 hr 2 minAudio

    My guest this week is James Brown, an engineering lead at Schroders, and that's a useful vantage point - asset managers carry all the regulation and organisational weight of a bank, mixed with the first-to-market...

    Credit the people on this episode

  5. What If Every SQL Query Could Update Incrementally? (with Lalith Suresh)

    Jul 8, 20261 hr 5 minAudio

    There's a problem that's bugged the database industry since the 1980s: you run an expensive query over millions of rows, cache the result, and then a single new row arrives. Logically that's one small update, but most...

    Credit the people on this episode