Making 768 servers look like 1
hisamafahri
30 points
6 comments
July 16, 2026
Related Discussions
Found 5 related stories in 112.1ms across 9,716 title embeddings via pgvector HNSW
- Making 768 servers look like 1 aarvin_roshin · 22 pts · July 15, 2026 · 100% similar
- Scaling to 1M concurrent sandboxes in seconds thundergolfer · 47 pts · July 16, 2026 · 55% similar
- 118M Queries per Second on Neki joshmgross · 89 pts · September 11, 2026 · 47% similar
- Dumb servers, smart clients: Distributing OS images with Quarry Levitating · 20 pts · September 30, 2026 · 47% similar
- It's Like Having 150 Extra Engineers glimshe · 36 pts · September 03, 2026 · 47% similar
Discussion Highlights (4 comments)
alightsoul
Load balancers, microservices and horizontal scaling?
jdw64
Looks like the GIF is fully built out in code. It's really nice to look at, well made, and easy to understand too. I wonder what program or code they used. I'd love to know. p.sI thought it was a GIF, but it's an iframe. That was a nice little surprise.
aarvin_roshin
Previously: https://news.ycombinator.com/item?id=48925420
drdexebtjl
What about sequences? The example shows an auto-incrementing user ID. How’s that possible without contention between all shards? Is the proxy responsible for sequences? What about foreign keys? Do they all have to live on the same shard? How do you do distributed transactions? On cross-shard reads: how do you do sorting? And cross-shard joins? I’d love to be proven wrong, but I suspect the 768 servers look like 1 only on the very surface, and you’ll get wildly different characteristics from cross-shard and single-shard queries. I personally would prefer if they _didn’t_ look like 1 if they can’t behave like 1.