How should the company write its application to handle these database requests?
Configure the application to publish to an Amazon Simple Notification Service (Amazon SNS) topic. Subscribe the database to the SNS topic.
Configure the application to subscribe to an Amazon Simple Notification Service (Amazon SNS) topic. Publish the database updates to the SNS topic.
Use Amazon Simple Queue Service (Amazon SQS) FIFO queues to queue the database connection until the database has resources to write the data.
Use Amazon Simple Queue Service (Amazon SQS) FIFO queues for capturing the writes and draining the queue as each write is made to the database.
Explanations:
Amazon SNS is designed for sending messages to multiple subscribers (fan-out pattern), not for queueing or ensuring database write durability. It lacks ordering and delivery guarantees needed for reliable asynchronous updates.
Similar to Option A, this setup misuses SNS for reliable database writes. SNS is not suitable for asynchronous write queuing or database connection management, as it doesn’t ensure ordered or reliable delivery to a database.
Although SQS can help manage asynchronous requests, this option suggests queueing the databaseconnection, which is not feasible. SQS manages messages, not direct connections, and this does not handle actual database writes.
Using SQS FIFO queues ensures reliable, ordered message delivery. The queue can capture all write requests, draining them in sequence to the database to prevent lost writes and manage unpredictable traffic effectively.
I rank that the answer is:
Use Amazon Simple Queue Service (Amazon SQS) FIFO queues for capturing the writes and draining the queue as each write is made to the database.
To the best of my knowledge, the answer is:
Use Amazon Simple Queue Service (Amazon SQS) FIFO queues for capturing the writes and draining the queue as each write is made to the database.