About
One platform concept at a time, shown moving
Platform Protocols explains how real systems behave. The Journal goes deep on one platform engineering concept per issue. This app shows each mechanism in motion and makes sure you still remember it next month.
readThe JournalOne concept per issue, from first principles to production evidence.
doThe LabsRun the mechanism yourself and watch it fail and recover.
see & rememberThis appThe mechanism, animated. Tested, then reviewed on a schedule.
How a round works
- Watch the mechanism. Every card opens on a whiteboard sketch of the real behaviour, moving.
- Guess first. Pick a definition before the answer appears. A wrong guess still helps it stick.
- Read the why. How it works, where it bites, the trade-off, and the source behind every claim.
- Recall later. Concepts come back as tests, after 1, 3, 7, 21 and 60 days.
- Stop. Rounds end on purpose. The gap before the next review is part of how memory works.
Accuracy rules
Every card names the source behind its claims and quotes it where possible. Numbers marked illustrative show the shape of a mechanism; they are examples, not measurements.
Sources in the Resilience deck
- Google SRE book, “Addressing Cascading Failures”: sre.google
- Marc Brooker, “Timeouts, retries, and backoff with jitter”, Amazon Builders’ Library: aws.amazon.com
- David Yanacek, “Using load shedding to avoid overload”, Amazon Builders’ Library: aws.amazon.com
- Martin Fowler, “CircuitBreaker” (after Michael Nygard, Release It!): martinfowler.com
- Azure Architecture Center, “Bulkhead pattern”: learn.microsoft.com
- Stripe API reference, “Idempotent requests”: docs.stripe.com
- Reactive Streams specification: reactive-streams.org
- Vattani, Chierichetti & Lowenstein, “Optimal Probabilistic Cache Stampede Prevention”, VLDB 2015: PDF
Your progress
Progress is saved in this browser only.
© Saravanakumar Raju · Platform Protocols