Module 05 · Communication patterns · Drill

Communication patterns drill

Scenario prompts that check whether communication patterns is usable under pressure. Answer out loud, then compare.

4 prompts25 minNew

0 of 4 graded

Prompt 1
Design the real-time layer for a delivery-tracking app: 2 million daily users watch a courier's location update every few seconds, and occasionally send a message to the courier. Choose transports for each direction, explain how updates reach the right client across many servers, and handle reconnects.
Say your answer out loud first. Thirty seconds is enough.
Prompt 2
A checkout service writes the order, then calls inventory, email, shipping and analytics synchronously. Latency is 2 seconds and any outage fails checkout. Redesign it, choose the broker family, and show how you guarantee no order is lost and no email is sent twice.
Say your answer out loud first. Thirty seconds is enough.
Prompt 3
You run a payments platform that notifies merchants of settled payments by webhook. Some merchant endpoints are slow, some are down for hours, and one registered an internal IP. Design the delivery system on your side and tell merchants how to build the receiving side.
Say your answer out loud first. Thirty seconds is enough.
Prompt 4
An image-processing pipeline consumes upload events from a FIFO queue partitioned by user. One corrupted upload makes the worker throw every time, and all later uploads from that user are stuck. Fix the immediate problem and redesign the failure path so it cannot recur.
Say your answer out loud first. Thirty seconds is enough.