[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"lesson-software-architecture-distributed-systems-and-data-en":3,"cheat-sheet---en":3,"topic-info----en":3,"prev-software-architecture-distributed-systems-and-data-en":3,"next-software-architecture-distributed-systems-and-data-en":3,"domain-info-software-architecture-distributed-systems-and-data-en":4},null,{"meta":5,"body":8},{"title":6,"description":7},"Distributed Systems and Data","The rules that change when a system spans machines: network fallacies, CAP, and consistency models. You design service communication, then replication, sharding, sagas, and CQRS for data that no longer fits one database.",{"type":9,"value":10,"toc":15},"minimark",[11],[12,13,14],"p",{},"This domain teaches the physics of distributed systems: what the network refuses to promise, what CAP actually says, and which consistency model your use case really needs. On that base you design service communication, then the data layer: replication, sharding, sagas for transactions that span services, and CQRS with event sourcing where reads and writes part ways.",{"title":16,"searchDepth":17,"depth":17,"links":18},"",3,[]]