A company’s ecommerce checkout workflow writes an order to a database and calls a payment service. Users experience timeouts during checkout; when they resubmit, multiple unique orders are created for the same transaction. How should a solutions architect refactor the workflow to prevent multiple orders?

Storing the order in the database first ensures data persistence. Sending the order number to an Amazon SQS FIFO (First-In, First-Out) queue guarantees message ordering and exactly-once processing, which is crucial for preventing duplicate orders. The payment service retrieves the message, processes the order, and then deletes the message, ensuring that even if the client retries, the order is processed only once. Kinesis Data Firehose is for streaming data to destinations, not for reliable, ordered message processing between services. CloudTrail is for logging API activity, not for orchestrating application workflows. Amazon SNS is a publish/subscribe service that delivers messages to multiple subscribers, but it doesn't guarantee exactly-once delivery or message ordering for individual subscribers in the same way SQS FIFO does, making it unsuitable for preventing duplicate orders in this scenario.