---
answer: direct
beat: system-design
source: 1 article · updated: November 17, 2026
---

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 Database

Sharding scales a database past one machine's limits, but it changes joins, transactions, and query patterns. Here's what each strategy trades away.

Crashtech Editorial November 17, 2026 System Design & Architecture

Read the full analysis

Other questions this article answers

More system design & architecture questions

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.