Building a High-Performance Ticketing System with TigerBeetle
38 points by nickmonad
38 points by nickmonad
Why is Redis in here along with Postgres? And we still end up at only 1000/reqs/s? How many data stores does one need to hit 1000/reqs/s with reliability? I am getting 100 locally, anyway.
The elegance of doc/tigerbeetle.md is hard to underestimate though. Reminds me of Statecharts.
Imagine this same architecture in Go, where removing Python’s 5ms overhead could yield 10-30x better throughput.
I guess the 1000 comes from (2 processes * 1 second / 5 ms) = 800 requests/second, which, assuming 5ms is more like 4.3 .. 4.5 ms to the presented 1000 requests
Making amateur concert ticketing systems should become a common school project in order to unseat the monopolies