---
title: "Discussion on \"Real-Time APIs: WebSockets vs Server-Sent Events\" | Hashnode"
description: "Discussion on \"Real-Time APIs: WebSockets vs Server-Sent Events\". REST is request-response. You ask, server answers, connection closes. Works fine for most things.\nBut chat messages can't wait for you to ask. Stock prices need to push the moment they change. Notifications should appear, not be polled for.\nTwo optio..."
url: "https://hashnode.com/posts/real-time-apis-websockets-vs-server-sent-events/6971a2f9991e086250d91a60"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Real-Time APIs: WebSockets vs Server-Sent Events](https://apiverve.hashnode.dev/real-time-apis-websockets-vs-server-sent-events?utm_source=hashnode&utm_medium=feed)

REST is request-response. You ask, server answers, connection closes. Works fine for most things. But chat messages can't wait for you to ask. Stock prices need to push the moment they change. Notifications should appear, not be polled for. Two optio...

Jan 22 · 10 min read · apiverve.hashnode.dev  
Updated Mar 16  
Read the article

-   [#architecture](https://hashnode.com/tag/architecture)
-   [#real-time](https://hashnode.com/tag/real-time)
-   [#server-sent-events](https://hashnode.com/tag/server-sent-events)
-   [#websockets](https://hashnode.com/tag/websockets)

## Written by

[APIVerve Team](https://hashnode.com/@apiverve)

@apiverve

  
[View profile](https://hashnode.com/@apiverve)

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
