Dead Letter Queue in Microservices: Handling Poison Messages
Learn how to design a dead letter queue in microservices: classify poison messages, bound message retry, enrich failures, and run safe DLQ replay with owners.
13 min read
Tag
Learn how to design a dead letter queue in microservices: classify poison messages, bound message retry, enrich failures, and run safe DLQ replay with owners.
13 min read
A checklist for backward compatible API changes: safe vs breaking changes, tolerant readers, expand-and-contract, enums, Protobuf and event rules, and CI checks.
18 min read
Build an inbox pattern for idempotent consumers: choose dedup keys, design a processed messages table, handle concurrency, retention, testing and trade-offs.
13 min read
A tiered approach to local development for microservices: Docker Compose for what you change, WireMock stubs for the rest and ephemeral previews.
13 min read
Why service to service authentication needs both workload and user identity, and how mTLS, JWT propagation and OAuth token exchange fit into one layered design.
13 min read
How to scope, version, deprecate and support shared libraries across microservices so each service upgrades on its own schedule while drift stays bounded.
14 min read
Learn how to classify dependencies, choose fallback responses, signal degraded results, and wire timeouts, retries and circuit breakers in microservices.
13 min read
Compare Redis Pub/Sub and Streams: delivery semantics, consumer groups, durability limits, crash recovery, and when each fits service-to-service messaging.
14 min read
Learn how to design bulkheads in microservices as a capacity-planning exercise: isolate thread pools and connections, size them with Little's Law, and verify.
12 min read
Learn how to split a monolith database by mapping joins first, assigning table ownership, and migrating one reversible stage at a time with safe rollbacks.
15 min read
Build CQRS read models across microservices: event design, idempotent projection, ordering, outbox vs CDC, rebuilds, staleness and when to avoid it.
14 min read
A step-by-step playbook to merge microservices into a modular monolith: when to do it, how to consolidate code and data safely, and what it costs.
13 min read