Exam AWS Certified Solutions Architect - Associate SAA-C03 topic 1 question 181 discussion

Option B, using Amazon Simple Notification Service (SNS), would not be suitable for this use case, as SNS is a pub/sub messaging service that is designed for one-to-many communication, rather than point-to-point communication between specific microservices. Option C, using an AWS Lambda function to pass messages, would not be suitable for this use case, as it would require the data producers and data consumers to have a direct connection and invoke the Lambda function, rather than being decoupled through a message queue. Option D, using an Amazon DynamoDB table with DynamoDB Streams, would not be suitable for this use case, as it would require the data consumers to continuously poll the DynamoDB Streams API to detect new table entries, rather than being notified of new data through a message queue.

A. Creating an Amazon SQS queue allows for asynchronous communication between microservices, decoupling the data producers and consumers. It provides scalability, flexibility, and ensures that data processing can happen independently and at a desired pace. B. Amazon SNS is more suitable for pub/sub messaging, where multiple subscribers receive the same message. It may not be the best fit for sequential data processing. C. Using AWS Lambda functions for communication introduces unnecessary complexity and may not be the optimal solution for sequential data processing. D. Amazon DynamoDB with DynamoDB Streams is primarily designed for real-time data streaming and change capture scenarios. It may not be the most efficient choice for sequential data processing in a microservices architecture.

A for sure

To Decouple a monolithic application - SQS - SQS standard - not in order - SQS FIFO - in order

Data is processed sequentially, but the order of results does not matter => SQS; if order matters => SQL FIFO

A is the answer.

Data is processed sequentially, but the order of results does not matter = Amazon Simple Queue Service

A) Create an Amazon Simple Queue Service (Amazon SQS) queue. Add code to the data producers, and send data to the queue. Add code to the data consumers to process data from the queue. For asynchronous communication between decoupled microservices, an SQS queue is the most appropriate service to use. SQS provides a scalable, highly available queue to buffer messages between producers and consumers. The order of processing does not matter, so a queue model fits well. The consumers can scale independently to process messages from the queue.

BBBBBBBBB

SQS for decoupling a monolithic architecture, hence option A is the right answer.

it also says 'the order of results does not matter'. Option B is correct.

The answer is A. B is wrong because SNS cannot send events "directly" to ECS. https://docs.aws.amazon.com/sns/latest/dg/sns-event-destinations.html

it deosn;t say it is one-one relationships , SNS is better

Best answer is A. Though C or D is possible it requires additional components and integration and so they are not efficient. Assuming that rate of incoming requests is within limits that SQS can handle A is best option.

A is correct

answer is B. An Amazon Simple Notification Service (Amazon SNS) topic can be used for communication between the microservices in this scenario. The data producers can be configured to publish notifications to the topic, and the data consumers can be configured to subscribe to the topic and receive notifications as they are published. This allows for asynchronous communication between the microservices, Question here focus on communication between microservices

We need decoupling so ok to use SQS