jorangreef

7 ms·

31.
by jorangreef 11mo ago
The author graciously gifted the domain to us and we’re literally days away from launching original TigerStyle here.
32.
by jorangreef 11mo ago
Yes, thanks! I don’t think we reviewed your Go benchmarking code at the time—and that there were no technical critiques probably should not have been taken as explicit sign off. IIRC we were more concerned at the deeper conceptual misunders
33.
by jorangreef 11mo ago
You would use TigerBeetle for everything: not only the final purchase transaction, but the shopping cart process, inventory management and queuing/reserving. In other words, to count not only the money changing hands, but also the corr
34.
by jorangreef 11mo ago
Appreciate your kind words, Kelsey! I searched the recent history of our community Slack but it seems it may have been an older conversation. We typically do code review work only for our customers so I’m not sure if there was some misunder
35.
by jorangreef 11mo ago
If only. But you also need to fix the internal concurrency control of the DBMS storage engine. TB here is very different to PG. For example, if you have 8K transactions through 2 accounts, a naive system might read the 2 accounts, update th
36.
by jorangreef 11mo ago
Thanks Kelsey! We’d love to roll up our sleeves and help you get it right. Please drop me an email.
37.
by jorangreef 11mo ago
Of course, there’s nothing new except shining a spotlight (and coining the rule!).
38.
by jorangreef 11mo ago
I’m not convinced that it’s confusing, or that there’s a better alternative—but I appreciate your critique. Do you not think if someone can remember those four words, they’re less likely to get it wrong? If you could contribute some better
39.
by jorangreef 11mo ago
The what here is the “system of record”. There might also be no other systems to write to/read from—and that's fine. The important thing is the order. Hopefully "Write Last, Read First" is unforgettable in that respect
40.
by jorangreef 11mo ago
Yes, write last to the system of record, read first from the system of record. Or in other words, commit to the system of record, and then read from the system of record to see what's committed. (This is similar also to how chain repli
41.
by jorangreef 11mo ago
I think the drop in non-batch performance was more a function of the PoC than of TB. Would love to see what our team could do for you here! Feel free to reach out to peter@tigerbeetle.com
42.
by jorangreef 11mo ago
You don't have to be an expert to understand Amdahl's Law. Definitely watch the talk if you haven't already: https://www.youtube.com/watch?v=yKgfk8lTQuE
43.
by jorangreef 11mo ago
> you risk getting bottlenecked by all the attributes you'll need to wrap around the transaction in PostgreSQL to make it work in a real application. The performance killer is contention, not writing any associated KV data—KV stores
44.
by jorangreef 11mo ago
> We didn't observe any automatic batching when testing Tigerbeetle with their Go client. This is not accurate. All TigerBeetle's clients also auto batch under the hood, which you can verify from the docs [0] and the source [1]
45.
by jorangreef 11mo ago
Joran from TigerBeetle! > For processing transactions one-by-one individually If you're artificially restricting the load going into TigerBeetle, by sending transactions in one-by-one individually, then I think predictable latency (
46.
by jorangreef 11mo ago
The short answer is that we tried, back in 2020, while working on a central bank payment switch by the Gates Foundation. We found we were hitting the limits of Amdahl's Law, given Postgres' concurrency control with row locks held
47.
by jorangreef 11mo ago
> Selling an event out takes a long time to do frequently because tickets are VERY frequently not purchased--they're just reserved and then they fall back into open seating. TigerBeetle actually includes native support for "two
48.
by jorangreef 11mo ago
Joran from TigerBeetle! Happy to answer any questions. And thanks to Dominik Tornow of Resonate for writing this up as a guest post! It was a little rule we had coined, to help people remember how to preserve consistency across different DB
49.
by jorangreef 11mo ago
Thank you for defending (handcrafted) art! :)
50.
by jorangreef 11mo ago
Thanks, appreciate your kind words! Yes, everything we do at TigerBeetle is handcrafted (by humans) for quality, including the art. Joy Machs on our team is an artist, and as you spotted, he signs all his work—I always ask him to! :) Joy al
51.
by jorangreef 11mo ago
Thanks! Zig is actually perfect for production network services (that’s all TB is essentially, or how I see it, and what I was looking for in Zig—how to create something with explicit limits that can handle overload—it’s hard to build anyth
52.
by jorangreef 11mo ago
“done” or “done as well”?
53.
by jorangreef 11mo ago
We could not have written TigerBeetle, at least not the way it is, without Zig: https://tigerbeetle.com/blog/2025-10-25-synadia-and-tigerbee...
54.
Building a high-performance ticketing system with TigerBeetle(renerocks.ai)
163 points by jorangreef 11mo ago|45 comments
55.
by jorangreef 11mo ago
Great to hear! Would love to learn more, if you’d like to drop me a note! (my email address is in my profile)
56.
by jorangreef 1y ago
Apologies, the context is the talk, and we didn’t submit this submission of the visualizer to HN! We are working on a tutorial stage, but people tend to hear about TB and TigerStyle and our DST first, appreciating the talks and that we make
57.
by jorangreef 1y ago
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 wit
58.
by jorangreef 1y ago
More precisely, “TigerBeetle’s hardest correctness challenges can’t be solved by language AT ALL”. The “harder problems” in TigerBeetle then (and where we invested millions literally in engineering): - distributed system strict serializabil
59.
by jorangreef 1y ago
Glad to hear! Let me invert our roles! What are 3 of some of the hardest correctness problems in TigerBeetle—and how does TigerBeetle solve them? Hint: None of these would be solved by language.
60.
by jorangreef 1y ago
Was this a question or a statement? :) (I appreciate both, let me add!) But sincerely, I think we don’t share the same philosophy: End to end correctness of software is a systems design problem, not a language problem. I believe that if you

More ›