Skip to main content

Quarantine and replay without rewriting history

This generated surface maps a learner-facing curriculum unit to its canonical source routes.

Curriculum surface​

  • Open learner-facing unit
  • Curriculum path: content/curriculum/production/semester-08-system-design-leadership/module-03-event-driven-architecture/concepts/cluster-06-saga-recovery/18-poison-replay.md
  • App: production
  • Semester: semester-08-system-design-leadership
  • Module: module-03-event-driven-architecture
  • Unit kind: concept
  • Curation level: module_curated

Learning objectives​

  • Explain Quarantine and replay without rewriting history in terms of events, temporal coupling, and consistency tradeoffs instead of diagram-first messaging vocabulary.
  • Use Quarantine and replay without rewriting history to predict how data, retries, ordering, and observability will behave when workflows are split across asynchronous boundaries.
  • Use microservices-patterns to connect the learner explanation to streams, event contracts, choreography, and coordination failure modes.

Prerequisites​

  • Comfort with service decomposition, distributed communication, and consistency tradeoffs from the earlier modules.

Source books​

  • microservices-patterns

Source routes​

Microservices Patterns​

Supporting curriculum routes​

No supporting curriculum routes linked yet.

External enrichment​

AI companion modes​

  • Explain simply
  • Socratic tutor
  • Challenge my understanding
  • Diagnose my confusion
  • Connect forward / backward

Source-of-truth note​

This teaching unit is learner-facing guidance. Its canonical source backbone is the referenced book microservices-patterns, and outside material should only clarify or strengthen that backbone.