Which services are commonly used for asynchronous messaging in decoupled architectures?

• A. Amazon SNS
• B. All of the above
• C. Amazon SQS
• D. Amazon EventBridge

Answer: (B)

In asynchronous messaging for decoupled architectures, you want services that let producers publish events without waiting for downstream processing, so components can scale independently. Amazon SNS enables publish-subscribe messaging: a producer sends a message to a topic and multiple subscribers—such as Lambda functions, SQS queues, or HTTP endpoints—receive it. This is great for fan-out and broad notification patterns while keeping producers decoupled from how messages are processed. Amazon SQS provides durable queues where producers place messages and consumers pull them for processing, which buffers load, ensures reliable delivery, and decouples service components with at-least-once processing (standard queues) or strict ordering (FIFO queues). Amazon EventBridge acts as an event bus that routes events from many sources to a wide range of targets using rules and filters, enabling loose coupling and scalable event-driven workflows across services and accounts.

All three are commonly used for asynchronous messaging in decoupled architectures, each fitting different needs—the pub/sub style with SNS, queue-based decoupling with SQS, and event-driven routing with EventBridge. In practice you might even blend them, such as publishing to SNS to fan out to multiple SQS queues or routing events through EventBridge to various targets.