Large-Scale Systems

Partitions are not optional, so the real choice is who waits when the line is cut. What the theorem actually says, two kinds of consistency that share a word, and the dial the whole season was quietly turning.

<p>The contract between services. Functions over a wire versus resources over verbs, what a good contract promises, and the single front door that does everything except business logic.</p>

The contract between services. Functions over a wire versus resources over verbs, what a good contract promises, and the single front door that does everything except business logic.

<p>Requirements that shape architecture, made measurable. Features versus attributes versus constraints, why several attributes contradict, and the number you promise that you now have to measure forever.</p>

Requirements that shape architecture, made measurable. Features versus attributes versus constraints, why several attributes contradict, and the number you promise that you now have to measure forever.

<p>The tier that collects, stores, searches, and processes what the application cannot. Shippers and sorters, the search index, the distributed file system, map-reduce, and the engine that kept the data in memory.</p>

The tier that collects, stores, searches, and processes what the application cannot. Shippers and sorters, the search index, the distributed file system, map-reduce, and the engine that kept the data in memory.

<p>Four families that made the scale trade explicit. The ring, the tablet, the column family, and the document; what each gives up, and the two decisions that make or break any of them.</p>

Four families that made the scale trade explicit. The ring, the tablet, the column family, and the document; what each gives up, and the two decisions that make or break any of them.

<p>What the consistency-first store gives up when it grows. The single-node ceiling, the cost hidden inside each strength, reads that scale and writes that do not, and the teams that sharded the relational model instead...

What the consistency-first store gives up when it grows. The single-node ceiling, the cost hidden inside each strength, reads that scale and writes that do not, and the teams that sharded the relational model instead of...

<p>The brokers. Push versus pull, delete-on-acknowledge versus the retained log, fire-and-forget, the cloud equivalents on three doors, and the one consumer rule at-least-once delivery forces.</p>

The brokers. Push versus pull, delete-on-acknowledge versus the retained log, fire-and-forget, the cloud equivalents on three doors, and the one consumer rule at-least-once delivery forces.

<p>The two cache products, chosen by access pattern. Cache-aside, the ring that lets you add a node without losing everything, what one forgets and the other remembers, and why the hard part is never speed.</p>

The two cache products, chosen by access pattern. Cache-aside, the ring that lets you add a node without losing everything, what one forgets and the other remembers, and why the hard part is never speed.