Patterns, companies and the systems we build, one narrated diagram at a time.
Keep one failing dependency from taking everything down.
0 of 4 watchedChange data in more than one place without losing or doubling anything.
0 of 5 watchedSpread load across many machines and keep them from drowning.
0 of 5 watchedLet services react to what happened, and make long processes finish.
0 of 5 watchedShape what clients see, and keep the contract honest as both sides change.
0 of 6 watchedServe the same answer cheaply, close to the reader, without serving it wrong.
0 of 3 watchedReplace and change running systems without a big-bang rewrite.
0 of 4 watchedContain failures so most users never notice them.
0 of 4 watched