Choose Client-Service Communication Protocols for Scale

Quick Overview

Compare client-service protocols for scalability, including HTTP requests, polling, event streams, WebSockets, backpressure, and reconnect recovery.

Choose Client-Service Communication Protocols for Scale

Company: Millennium

Role: Software Engineer

Category: System Design

Difficulty: medium

Interview Round: Technical Screen

Explain how you would choose communication protocols between a client and backend services, and how those choices affect scalability. Compare ordinary request/response interactions with server-driven updates and long-lived connections. ### Constraints & Assumptions No application workload or latency target is specified. Frame the choice around the client's communication pattern and operational requirements rather than assuming every interaction needs real-time streaming. ### Clarifying Questions to Ask - Are updates initiated by the client, the server, or both? - Are clients browsers, mobile apps, or trusted backend services? - How frequent are messages, and must disconnected clients recover missed events? ```hint Count idle connections and repeated requests Two protocols with similar message sizes can impose very different connection and retry costs. ``` ### What a Strong Answer Covers - Request/response APIs versus polling, server-sent events, and bidirectional connections. - Load balancing, connection state, backpressure, and reconnect behavior. - Idempotency and authentication across retries or reconnects. ### Follow-up Questions - How would you prevent a mass reconnect from overwhelming the service? - Where would you store resumable event positions if any frontend instance may serve a client?

Overview: Compare client-service protocols for scalability, including HTTP requests, polling, event streams, WebSockets, backpressure, and reconnect recovery.

Read the full Millennium Software Engineer interview experience this question came from

Millennium logo
Millennium
Nov 17, 2026
mediumSoftware EngineerTechnical ScreenSystem Design
1
0

Explain how you would choose communication protocols between a client and backend services, and how those choices affect scalability. Compare ordinary request/response interactions with server-driven updates and long-lived connections.

Constraints & Assumptions

No application workload or latency target is specified. Frame the choice around the client's communication pattern and operational requirements rather than assuming every interaction needs real-time streaming.

Clarifying Questions to Ask Guidance

  • Are updates initiated by the client, the server, or both?
  • Are clients browsers, mobile apps, or trusted backend services?
  • How frequent are messages, and must disconnected clients recover missed events?

What a Strong Answer Covers Guidance

  • Request/response APIs versus polling, server-sent events, and bidirectional connections.
  • Load balancing, connection state, backpressure, and reconnect behavior.
  • Idempotency and authentication across retries or reconnects.

Follow-up Questions Guidance

  • How would you prevent a mass reconnect from overwhelming the service?
  • Where would you store resumable event positions if any frontend instance may serve a client?