What is the purpose of the persisted queue in the non-transactional reliability pattern?

What is the purpose of the persisted queue in the non-transactional reliability pattern?

• A. To persist messages while awaiting processing
• B. To lightly store messages before processing
• C. To persist messages for auditing
• D. To replace the input queue

Answer: (A)

In the non-transactional reliability pattern, the system buffers incoming messages in a persisted queue so they’re stored durably while they wait to be processed. This ensures messages aren’t lost if processing is delayed, the consumer is slow, or the app restarts, enabling at-least-once delivery by retrying processing for the persisted items. That’s why the best choice is to persist messages while awaiting processing. The other options describe lighter storage, auditing, or replacing the input queue, which don’t capture the durability and decoupling purpose of the persisted queue.

In the non-transactional reliability pattern, the system buffers incoming messages in a persisted queue so they’re stored durably while they wait to be processed. This ensures messages aren’t lost if processing is delayed, the consumer is slow, or the app restarts, enabling at-least-once delivery by retrying processing for the persisted items.

That’s why the best choice is to persist messages while awaiting processing. The other options describe lighter storage, auditing, or replacing the input queue, which don’t capture the durability and decoupling purpose of the persisted queue.