/architecture-events
Event-driven pipelines, fan-out patterns, and system design that scales down too.
How the pieces fit together: event notifications, queues, workers, retries, and the delivery guarantees you actually get in practice. Focused on architectures small teams can operate.
Build the SNS-to-SQS fan-out pattern where each consumer owns a private queue with its own retry policy and DLQ. Covers queue policies, raw message delivery, redrive config, and the delivery guarantees you actually get.
Both make your system asynchronous, but they solve different problems. Queue semantics vs topic semantics, when to reach for each, and the SNS → SQS fan-out pattern that shows up in real system designs.
Producers publish once; each consumer owns a private queue with its own retry policy and DLQ. Cleanly decouples deployments.