In the last article, I explained how to rebuild Event-Driven Read Models in a safe and resilient way. I asked readers to let me know if they find any blind spots in my design.

Architecture Weekly's publication is a central hub for architecture enthusiasts, offering insights into architectural design, urban planning, and sustainable architecture practices. Through articles, case studies, and architectural critiques, Architecture Weekly offers insights into iconic buildings, architectural trends, and innovative design solutions. Readers can learn about architectural history, design principles, and environmental sustainability initiatives to gain a deeper understanding of the built environment and its impact on society. Additionally, Architecture Weekly provides updates on the latest architectural projects, design competitions, and industry events to help architects and designers stay informed and inspired.

Architecture Weekly

Explores a race condition in event-driven read model rebuilding where events can be skipped during the transition from rebuilding to active status. After examining multiple failed coordination approaches (waiting for transactions, transaction ID boundaries, exclusive locking), the author proposes a Dead Letter Queue pattern: recording skipped events in a system messages table during the same transaction, then draining them after rebuild completion. The solution accepts that some failures are unavoidable in distributed systems and focuses on making them visible and recoverable rather than preventing them entirely.

On rebuilding read models, Dead-Letter Queues and Why Letting Go is Sometimes the Answer

Everyone has a plan until they get punched in the mouth