What is a typical use case that illustrates the need for asynchronous messaging?

What is a typical use case that illustrates the need for asynchronous messaging?

• A. Command-and-control requiring immediate response.
• B. Telemetry streams that can burst independently.
• C. Password reset prompts requiring confirmation.
• D. Acknowledge configuration changes only after a complete cycle.

Answer: (B)

Asynchronous messaging shines when components don’t need to wait for each other and can process work at their own pace. Telemetry streams are a perfect example: sensors generate data in bursts, and the analytics or storage system consumes it later or at its own rate. A message queue lets those bursts be buffered, decoupling producers from consumers, which makes the system more resilient to spikes and failures. This decoupled, burst-tolerant flow is the classic scenario that shows why asynchronous messaging is useful. The other options rely on immediate, coordinated interaction. Command-and-control requiring an immediate response needs synchronous, real-time communication. Password reset prompts needing confirmation involve user interaction and synchronous steps. Acknowledging configuration changes after a complete cycle implies coordination and timing that doesn’t leverage the decoupled, burst-friendly nature of asynchronous messaging.

Asynchronous messaging shines when components don’t need to wait for each other and can process work at their own pace. Telemetry streams are a perfect example: sensors generate data in bursts, and the analytics or storage system consumes it later or at its own rate. A message queue lets those bursts be buffered, decoupling producers from consumers, which makes the system more resilient to spikes and failures. This decoupled, burst-tolerant flow is the classic scenario that shows why asynchronous messaging is useful.

The other options rely on immediate, coordinated interaction. Command-and-control requiring an immediate response needs synchronous, real-time communication. Password reset prompts needing confirmation involve user interaction and synchronous steps. Acknowledging configuration changes after a complete cycle implies coordination and timing that doesn’t leverage the decoupled, burst-friendly nature of asynchronous messaging.