Part of this page failed to reach you. Reload to try again — if it keeps happening, check your connection.
This site needs JavaScript to display its content. Enable it in your browser and reload the page.
1 post filed under this tag.
I ran the same hot-key seat reservation workload two ways: Postgres with a version column and retries, and a single actor per seat. The actor design did not scale better — it moved the hard problem from concurrency control to routing and rebalance correctness, and that trade was the easier one to reason about under hot keys.