3 ms·

I'm not sure how many customers that Tiger Beetle have but I really hope they are successful. It would be great to see such a quality focused engineering org ma

I'm not sure how many customers that Tiger Beetle have but I really hope they are successful. It would be great to see such a quality focused engineering org make it. They are basically doing what many devs really want to do - make the highest quality and fastest stuff possible - instead of banging out random features that usually no one actually cares about. I don't have a use case for their tech right now, but the moment I have a need for anything in the vicinity I'll be checking it out..

jorangreef 1y ago
Thanks! Joran, CEO from TigerBeetle here! We’re doing pretty well as a business already, contrary to Rochus’ comment, which is not accurate. Our team is 16, we have $30M in investment, and already some of the largest brokerages, exchanges, and wealth managements, in their respective jurisdictions are customers of TigerBeetle. We have a saying: “Good engineering is good business, and good business is good engineering.” At least in TigerBeetle’s experience, the saying is proving true. We really appreciate your support and kind words!
- Rochus 1y ago
  Thanks for the clarifications. May I ask what made you use Zig instead of e.g. Rust or C++ (or even Ada/SPARK)? I assume Go would be too undeterministic for real-time applications?
  - bnolsen 1y ago
    Go doesn't belong in this discussion.its a better java, c#, python and not much more. It doesn't work for 24/7 or for performance sensitive applications.
    - Rochus 1y ago
      > Go doesn't belong in this discussion.its a better java, c#, python and not much more. It doesn't work for 24/7 or for performance sensitive applications. The claim is factually backwards. Go significantly outperforms Java, C#, and Python (~10x faster than Python, lower memory usage than C#), and runs successfully in countless 24/7 production systems including high-throughput APIs and distributed services. The actual valid concern, which made me question its suitability, is that Go wouldn't be appropriate for TigerBeetle's specific real-time requirements. TigerBeetle is a financial transaction database requiring deterministic, predictable microsecond-level latencies with strict timestamp ordering across a distributed consensus protocol. Go's garbage collector introduces unpredictable pauses that would likely violate these hard real-time guarantees.

jorangreef 1y ago

Thanks! Joran, CEO from TigerBeetle here! We’re doing pretty well as a business already, contrary to Rochus’ comment, which is not accurate. Our team is 16, we have $30M in investment, and already some of the largest brokerages, exchanges, and wealth managements, in their respective jurisdictions are customers of TigerBeetle. We have a saying: “Good engineering is good business, and good business is good engineering.” At least in TigerBeetle’s experience, the saying is proving true. We really appreciate your support and kind words!

Rochus 1y ago
Thanks for the clarifications. May I ask what made you use Zig instead of e.g. Rust or C++ (or even Ada/SPARK)? I assume Go would be too undeterministic for real-time applications?
- bnolsen 1y ago
  Go doesn't belong in this discussion.its a better java, c#, python and not much more. It doesn't work for 24/7 or for performance sensitive applications.
  - Rochus 1y ago
    > Go doesn't belong in this discussion.its a better java, c#, python and not much more. It doesn't work for 24/7 or for performance sensitive applications. The claim is factually backwards. Go significantly outperforms Java, C#, and Python (~10x faster than Python, lower memory usage than C#), and runs successfully in countless 24/7 production systems including high-throughput APIs and distributed services. The actual valid concern, which made me question its suitability, is that Go wouldn't be appropriate for TigerBeetle's specific real-time requirements. TigerBeetle is a financial transaction database requiring deterministic, predictable microsecond-level latencies with strict timestamp ordering across a distributed consensus protocol. Go's garbage collector introduces unpredictable pauses that would likely violate these hard real-time guarantees.