Replace Polling with Push

A web client polls a notification API every 5 seconds to check for new messages. Most polls return nothing, wasting requests and server capacity, and a real notification can be up to 5 seconds late. Switch to real-time delivery.

Context

Polling repeatedly asks the server "anything new?", wasting requests and capping latency at the poll interval. A push channel (WebSocket, SSE, or a pub-sub stream) lets the server deliver events the moment they occur, over a connection the client opens once. The trade-off is managing many persistent connections and their lifecycle (reconnection, backpressure).

Requirements

•Remove the periodic client polling loop
•Add a push channel (WebSocket, SSE, or a streaming layer) so the server pushes updates
•The client subscribes once and receives events as they happen

Non-Functional Requirements

•Update latency must not depend on a fixed polling interval

Constraints

•Focus on the push topology — ignore reconnection/backoff and message-ordering guarantees

Evaluation Criteria

Evaluation criteria and weights will be revealed after you submit your solution. This ensures a fair assessment of your design skills.

Ready to solve this challenge?

Draw your architecture diagram, explain your design decisions, and get AI-powered feedback.

For the best experience, design challenges on a desktop or tablet — drawing the architecture on a phone is hard.

Start drawing nowNo account needed to draw. Sign up only to see your score (2 free evaluations).Already have an account? Sign in