Limited Time Offer:Up to 0% off Hello Interview Premium
Up to 0% off Hello Interview Premium 🎉
Hello Interview
Learn System Design
Introduction
How to Prepare
Delivery Framework
Core Concepts
Key Technologies
Common Patterns
Question Breakdowns
Networking Essentials
API Design
Data Modeling
Caching
Sharding
Consistent Hashing
CAP Theorem
Database Indexing
Numbers to Know
Bitly
Dropbox
Local Delivery Service
Ticketmaster
FB News Feed
Tinder
LeetCode
WhatsApp
Rate Limiter
YouTube
FB Live Comments
YouTube Top K
Uber
Web Crawler
Ad Click Aggregator
FB Post Search
Yelp
Instagram
Strava
Distributed Cache
Online Auction
Job Scheduler
News Aggregator
Price Tracking Service
Notification System
Robinhood
Google Docs
Payment System
Metrics Monitoring
Online Chess
ChatGPT
Real-time Updates
Quick Reference
Dealing with Contention
Multi-step Processes
Scaling Reads
Scaling Writes
Handling Large Blobs
Managing Long Running Tasks
Redis
Elasticsearch
Kafka
API Gateway
Cassandra
DynamoDB
PostgreSQL
Flink
ZooKeeper
Proximity Search
Time Series Databases
Data Structures for Big Data
Vector Databases
All Posts
Shopify Inventory Reservations
New
Discord Message Storage
New
Slack Job Queue
New
Vote For New Content
Pricing
Sign in / Sign up
Search
⌘K
Pricing

Tutor

Get Premium
Hello InterviewQuick Reference
Full Article
Quick Reference
Premium

Real-time Updates

First Hop

Client Protocols

Client protocols: Simple Polling is the default unless low latency is required, Long Polling holds HTTP requests for infrequent near-real-time updates, Server-Sent Events is a one-way HTTP stream, WebSockets is a full-duplex persistent channel, and WebRTC is peer-to-peer with signaling, STUN, and TURN.
  • Simple Polling: Default unless low latency is required; stateless HTTP, delayed by the polling interval.
  • Long Polling: Held HTTP request gives near real-time for infrequent updates, but bursts add callback latency.
  • Server-Sent Events (SSE): One-way HTTP stream; efficient for server push when clients rarely write back.
  • WebSockets: Full-duplex persistent channel for high-frequency reads and writes; adds stateful infra.
  • WebRTC: Peer-to-peer for audio/video or server-load reduction; requires signaling, STUN, and TURN.

Load Balancers

Connection Pitfalls

Second Hop

Trigger Models

Scaling Assignment

Key Numbers

Interview Scenarios

Bidirectional Delivery Scenarios

High-Volume Fan-Out Scenarios

Consistency and Conflict Scenarios

Deep Dive Fixes

Purchase Premium to Keep Reading

Unlock this article and so much more with Hello Interview Premium
Buy Premium
Reading Progress

On This Page

First Hop

Client Protocols

Load Balancers

Connection Pitfalls

Second Hop

Trigger Models

Scaling Assignment

Key Numbers

Interview Scenarios

Bidirectional Delivery Scenarios

High-Volume Fan-Out Scenarios

Consistency and Conflict Scenarios

Deep Dive Fixes

Questions
Meta SWE Interview QuestionsAmazon SWE Interview QuestionsGoogle SWE Interview QuestionsOpenAI SWE Interview QuestionsAnthropic SWE Interview QuestionsEngineering Manager (EM) Interview Questions
Learn
Learn System DesignLearn DSALearn BehavioralLearn ML System DesignLearn Low Level DesignGuided Practice
Links
FAQPricingGift PremiumHello Interview Premium
Legal
Terms and ConditionsPrivacy PolicySecurity
Contact
About UsProduct Support

7511 Greenwood Ave North Unit #4238 Seattle WA 98103

© 2026 Optick Labs Inc. All rights reserved.