Course contentsShow
← System Design
Lesson 1673 of 1,91940. Real-World System: Social Media FeedFree lesson

Server-Sent Events (SSE) Alternative

Implementing unidirectional streaming from server to client using SSE for simpler real-time feed updates.

Server-Sent Events (SSE) Alternative

What you'll learn: How to use Server-Sent Events as a simpler alternative to WebSockets for pushing real-time feed updates to users.

The Core Idea

While WebSockets provide bidirectional communication, many social media feed scenarios only need one-way streaming: server to client. Server-Sent Events (SSE) is a lightweight HTTP-based protocol designed exactly for this. When a new post appears in a user's feed, the server pushes it down to the browser without the client asking.

Think of it like a news ticker: you tune in once, and updates keep scrolling by. You don't need to send messages back through the ticker—you just receive.

How SSE Works

SSE uses a long-lived HTTP connection where the server sends text-based events in a specific format:

data: {"type":"new_post","post_id":12345}

data: {"type":"like","post_id":12346}

The browser's EventSource API automatically reconnects if the connection drops, handles message parsing, and fires JavaScript events you can listen to.

SSE vs WebSocket for Feeds

SSE advantages:

  • Simpler implementation—just HTTP responses
  • Automatic reconnection built-in
  • Works through most proxies and firewalls
  • Lower overhead when you only push data one way

SSE limitations:

  • HTTP/1.1 connection limits per domain (~6)
  • Text-only (JSON works fine)
  • No client-to-server messaging (use separate REST calls)

For a social feed where the server pushes new posts, likes, and comments but user interactions happen via separate API calls, SSE is often the better architectural choice than WebSockets.

Key Takeaway: Server-Sent Events provide a simpler, HTTP-native solution for unidirectional real-time feed updates, reducing complexity when bidirectional communication isn't needed.