messaging-and-events

Use SQS for one-to-one messaging, SNS for one-to-many fan-out, EventBridge for event bus routing, and WebSockets for real-time client updates. This Skill provides a decision tree to map your decoupling requirements to the correct AWS service pattern.

The best way to decouple microservices is introducing asynchronous messaging to reduce coupling and improve resilience. This Skill guides selecting and configuring event flows like SQS or EventBridge for your specific migration scenario.

Use AWS EventBridge instead of SNS when you need an event bus to route events between multiple services with fine-grained filtering. SNS is better suited for simple one-to-many fan-out patterns without complex routing rules.

You configure SQS and SNS for background processing by wiring producers to send messages to queues or topics, and consumers to poll them. This Skill specifies recommended services and provides example configuration snippets for common scenarios.

Yes, you can use WebSockets for real-time updates in an event-driven architecture. This Skill outlines the real-time pattern to push live client updates alongside your asynchronous messaging backbone.

Yes, this messaging architecture guidance applies to modular monoliths, multi-service architectures, and monolith-to-microservice migrations. It helps teams specify decoupled event flows and asynchronous processing across various structural patterns.