3.7 Application Integration and Other Services

Quick Answer: Application-integration services let components communicate without tight dependencies. SQS is a pull-based message queue (one consumer per message), SNS is push-based pub/sub (every subscriber gets the message), EventBridge is a serverless event bus, Step Functions orchestrates workflows, and API Gateway fronts APIs. Together they enable the loosely coupled, resilient architectures AWS favors.

Messaging and Event Services

Amazon SQS (Simple Queue Service)

Amazon SQS is a fully managed message queue that decouples and scales microservices and distributed systems.

Example: an ordering front end drops orders into an SQS queue; worker instances process them at their own pace, so a traffic spike fills the queue instead of overwhelming the workers.

Amazon SNS (Simple Notification Service)

Amazon SNS is a pub/sub service that pushes one message to many subscribers at once.

SQS vs. SNS

On the Exam: SQS = one consumer per message (a queue). SNS = every subscriber gets it (broadcast). A classic combined pattern is SNS fan-out to multiple SQS queues, where one event triggers several independent processing pipelines.

Amazon EventBridge

Amazon EventBridge is a serverless event bus for event-driven architectures. Rules match incoming events and route them to targets; a schema registry discovers event structures; it also connects to SaaS partners. It was formerly CloudWatch Events.

Example: when an EC2 instance changes state, an EventBridge rule triggers a Lambda function to send a notification.

---

Workflow Orchestration

AWS Step Functions

Step Functions coordinates multiple AWS services into serverless workflows defined as state machines, with a visual designer plus branching, parallel execution, retries, and error handling. Use it for order processing, data pipelines, human-approval steps, and ML pipelines.

---

API Management

Amazon API Gateway

API Gateway creates, publishes, and manages REST, HTTP, and WebSocket APIs at any scale, with throttling, caching, API keys, and authorization built in. The canonical serverless backend is API Gateway + Lambda, with both scaling automatically and no servers to manage.

---

Developer, IoT, and End-User Services

---

Migration, Marketplace, and Other Services

On the Exam: Watch the difference between AWS Marketplace (buy third-party/AWS software) and AWS Service Catalog (publish your own approved products internally). Both are "catalogs," but for opposite audiences.

---

Why Decoupling Matters

The reason these services appear so often is that AWS architecture strongly favors loose coupling. When components call each other directly, a slowdown or failure in one cascades into the others, and you cannot scale or update pieces independently. Inserting a queue (SQS), a topic (SNS), or an event bus (EventBridge) between components breaks that chain: a failed consumer simply leaves messages in the queue until it recovers, and each side scales on its own.

This pattern maps directly to the Reliability and Performance Efficiency pillars of the Well-Architected Framework. Expect "decouple the components" scenarios where the right answer is SQS, SNS, or EventBridge rather than a direct, synchronous connection. A buffering queue in front of a processing tier is also the standard way to absorb sudden traffic spikes without dropping work.

One more distinction worth memorizing: SQS and SNS handle messages, while Step Functions handles workflows and EventBridge handles events. If a scenario describes coordinating an ordered, multi-step process with branching and retries, the answer is Step Functions, not a raw queue. If it describes reacting to a state change emitted by an AWS service or SaaS app, the answer is EventBridge. Reading for "message," "event," or "multi-step workflow" usually selects the right service on the first pass.