What is a cross-shard transaction, and why is it a real engineering problem?
A cross-shard transaction is one that needs to atomically update rows living on two or more different shards — e.g. transferring money between two users whose accounts happen to live on different shards. A single database's ACID transaction guarantees don't extend across separate machines automatically; achieving atomicity across shards requires distributed transaction protocols (like two-phase commit) or careful application-level compensation logic, both of which add real complexity and latency.
Answered in
Database Sharding: What It Actually Costs When You Split the DatabaseSharding scales a database past one machine's limits, but it changes joins, transactions, and query patterns. Here's what each strategy trades away.
Read the full analysisOther questions this article answers
More system design & architecture questions
- How much spare capacity should a gateway keep?
- Why are bounded queues important for availability?
- Should a load balancer always move requests away from an unhealthy server?
- Can a circuit breaker prevent every cascading failure?
- Why does pagination improve API performance beyond just 'smaller responses'?
- Why is asynchronous logging faster than writing logs synchronously?
- When does caching actually help API performance, and when doesn't it?
- Why does payload compression trade CPU time for network time, and when is that worth it?
Every answer on Crashtech is written by the editor of the article it comes from — never auto-summarised. Browse all answers or the System Design & Architecture beat.