Cache-aside
Load repeated reads into a cache while keeping SQL authoritative.
Explore the flow, stress a failure, then practice.
Learn this patternExplore system architecture, application structure, caching, messaging, reliability and data consistency. Follow a request, introduce a failure, then apply what you learn in a challenge.
Go to practice challenges →14 of 14 patterns
Load repeated reads into a cache while keeping SQL authoritative.
Explore the flow, stress a failure, then practice.
Learn this patternBuffer bursts and let workers consume at a sustainable rate.
Explore the flow, stress a failure, then practice.
Learn this patternStop repeated calls to a failing dependency and probe recovery deliberately.
Explore the flow, stress a failure, then practice.
Learn this patternCommit a business change and its event record in one database transaction.
Explore the flow, stress a failure, then practice.
Learn this patternSeparate commands from queries and build read models for the questions users ask.
Explore the flow, stress a failure, then practice.
Learn this patternCoordinate local transactions and compensate completed business steps after failure.
Explore the flow, stress a failure, then practice.
Learn this patternSeparate the client experience from authoritative server decisions.
Explore the flow, stress a failure, then practice.
Learn this patternGive presentation, application, domain and persistence distinct responsibilities.
Explore the flow, stress a failure, then practice.
Learn this patternDeliver one published event to independent subscriptions with their own progress.
Explore the flow, stress a failure, then practice.
Learn this patternCompose transformations as stages with explicit input, output and recovery boundaries.
Explore the flow, stress a failure, then practice.
Learn this patternCoordinate reactions to facts through explicit event contracts and delivery semantics.
Explore the flow, stress a failure, then practice.
Learn this patternChoose independently deployable business boundaries and explicit service-owned state.
Explore the flow, stress a failure, then practice.
Learn this patternKeep domain events as the authoritative history and derive current state by replay.
Explore the flow, stress a failure, then practice.
Learn this patternCompare three ways to protect business rules through inward-facing source dependencies.
Explore the flow, stress a failure, then practice.
Learn this pattern