FAfanf2·Dec 26, 2025Submission
Vulcain: HTTP/2 server push for fast and idiomatic client-driven REST APIs
9 points · Open discussiondunglas
vulcain
Go2019–2025
dunglas / vulcain
vulcain
🔨 Fast and idiomatic client-driven REST APIs.
7Distinct people
8Mentions
0Explicit recommenders
3.6KGitHub stars
What to know before exploring
What it is
🔨 Fast and idiomatic client-driven REST APIs.
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: 2019-10-13 12:01:49 UTC to 2025-12-26 09:42:02 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 |
|---|---|---|---|---|---|
| 2019 | 2019-01-01 00:00:00 UTC | 2020-01-01 00:00:00 UTC | 2 | 1 | 1 |
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 3 | 0 | 3 |
| 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 | 1 | 0 | 1 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 1 | 1 | 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 sourcesFast and idiomatic client-driven REST APIs
1 points · Open discussionFunny thing is that I was just looking into how this software could work with APIs and now it seems like it's dead in the water if the support is removed from the browser. Sure, it's a progressive enhancement and you wouldn't break anything, but you lose all the benefit as far as I can tell and you _are_ adding an extra layer.
https://github.com/dunglas/vulcain
In Removing HTTP/2 Server Push from Chrome> Yeah this works well for specifically this case.
What do you think of the opinion of Kévin Dunglas (Vulcain) in this case. Too optimistic?
See:
https://github.com/dunglas/vulcain/issues/70#issuecomment-72...
In HTTP/2 Push is deadVulcain ( https://github.com/dunglas/vulcain ) is another example of getting GraphQL's benefits on top of existing technology.
In A REST View of GraphQLThat sounds pretty much like what Vulcain [1] is doing for you on top of an existing REST API.
[1] https://github.com/dunglas/vulcain
In A REST View of GraphQLThanks for the feedback! I just added a section in the README to clarify things about the license: https://github.com/dunglas/vulcain#license-and-copyright
* proprietary software can implement the Vulcain specification
* proprietary software can be used behind the Vulcain Gateway Server without having to share their sources
* modifications made to the Vulcain Gateway Server must be shared
* alternatively, a commercial license is available for the Vulcain Gateway Server
In Vulcain: A REST-Based Alternative to GraphQLVulcain: A REST-Based Alternative to GraphQL
61 points · Open discussion