1,742
1,740
1,7371,7371,7361,7361,736495495
435431314314
188Apr 16 · 21 min read · The failure scenario At 09:14:33, a customer places a £29.99 order on your platform. The order is saved to the database. The process crashes before publishing order.created to RabbitMQ. The fulfilment
Join discussion
Apr 1 · 5 min read · There's a moment when you're building a backend where you realize that not everything needs to happen immediately. A user uploads a video — do they need to wait 2 minutes for it to be transcoded befor
Join discussionMar 23 · 23 min read · Spry Ecosystem Integrations: Databases, Caching, Message Queues, and External APIs Modern applications don't exist in isolation. In this comprehensive guide, we'll explore how to integrate Spry – the next‑generation Dart server framework – with the b...
Join discussionMar 13 · 14 min read · TLDR: A dead letter queue protects throughput by moving repeatedly failing messages out of the hot path. It only works if retries are bounded, triage has an owner, and replay is a deliberate workflow instead of a panic button. TLDR: The main SRE ques...
Join discussionMar 12 · 13 min read · TLDR: Message queues and event-driven architecture let services communicate asynchronously, absorb bursty traffic, and isolate failures. The core design challenge is not adding a queue — it is defining delivery semantics, retry behavior, and idempote...
Join discussionMar 9 · 13 min read · TLDR: Kafka is a distributed event store. Unlike a traditional queue (RabbitMQ) where messages disappear after reading, Kafka stores them in a persistent Log. This allows multiple consumers to read the same data at their own pace, replay history, and...
Join discussion
