POporjo·Jan 2, 2025Submission
Mercure: A WebSocket alternative for server-sent events
156 points · Open discussiondunglas
mercure
Go2018–2025
dunglas / mercure
mercure
🪽 An open, easy, fast, reliable and battery-efficient solution for real-time communications
8Distinct people
8Mentions
0Explicit recommenders
5.4KGitHub stars
What to know before exploring
What it is
🪽 An open, easy, fast, reliable and battery-efficient solution for real-time communications
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year8 dated mentions
Observed mentions: 2018-10-11 13:01:57 UTC to 2025-01-02 04:33:12 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2018 | 2018-01-01 00:00:00 UTC | 2019-01-01 00:00:00 UTC | 5 | 4 | 1 |
| 2019 | 2019-01-01 00:00:00 UTC | 2020-01-01 00:00:00 UTC | 2 | 2 | 0 |
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2025 | 2025-01-01 00:00:00 UTC | 2026-01-01 00:00:00 UTC | 1 | 1 | 0 |
What Hacker News says
8 sourcesMercure: A Protocol for Server-Sent Live Updates
2 points · Open discussionMercure: Full duplex server sent events
1 points · Open discussionMercure – server-sent live updates: protocol and reference implementation
1 points · Open discussionMercure: Server-sent live updates – protocol and reference implementation
2 points · Open discussionThey address this in the README of the repo (https://github.com/dunglas/mercure) under the "What's the Difference Between Mercure and WebSocket?" section:
> WebSocket is a low level protocol, Mercure is a high level one. Mercure provides convenient built-in features such as authorization, re-connection and state reconciliation ; while with WebSocket, you need to implement them yourself. Also, unlike Mercure (which is built on top of HTTP and Server-Sent Events), WebSocket is not designed to leverage HTTP/2.
> HTTP/2 connections are multiplexed and bidirectional by default (it was not the case of HTTP/1). When using Mercure over a h2 connection (recommended), your app can receive data through Server-Sent Events, and send data to the server with regular POST (or PUT/PATCH/DELETE) requests, with no overhead.
In A real-time chat app in 23 lines of Python and 35 lines of JavaScriptA real-time chat app in 23 lines of Python and 35 lines of JavaScript
42 points · Open discussionMercure, Server-Sent Live Updates
3 points · Open discussion