HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
uNetworking
uWebSockets
C++2016–2025
uNetworking / uWebSockets

uWebSockets

Simple, secure & standards compliant web server for the most demanding of applications

33Distinct people
46Mentions
1Explicit recommenders
19KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Simple, secure & standards compliant web server for the most demanding of applications

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

Just WebSockets in a C++ server. I have my own implementation that I wrote from the scratch because when I started µWS [1] didn't even exist yet. I recommend their…

Matheus28 used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 4:59:52 AM 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 year46 dated mentions

Observed mentions: 2016-05-17 14:09:05 UTC to 2025-11-17 21:05:08 UTC.

0510152016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 14 mentions; 6 submissions, 8 comments20162017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 7 mentions; 1 submissions, 6 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments20202021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 12 mentions; 1 submissions, 11 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2025

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC1468
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC716
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC101
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC202
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC110
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC404
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC12111
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC202
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC000
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC303

What Hacker News says

12 sources
Not exaclty -- it looks like it's pretty overkill for my needs I'm looking for something more like websocketpp[0], or even just grpc without a requisite proxy. uWebsockets looks really promising, being header only, but in the fine print requires a runtime library. unfortunately, none of that ecosystem seems to use cmake, making integrating it that much more of a pain. why use cpp for this, I'm sure some HNer will ask. the ray tracer itself is using cuda, that's why. I've also debated - running it as a grpc server and having some proxy in a more web-accessible language - creating python bindings and using python to make a websocket/http server for it neither of those are out of the question, but they're not my first choices, because I'd like to keep the build & execution simple. introducing dependencies, especially other executables,
Read the rest
is in conflict with that. i don't need anything particularly scalable -- a threaded implementation, or one using select() would be fine, if not preferable. [0] https://docs.websocketpp.org/ [1] https://github.com/uNetworking/uWebSockets
In Nuklear – A single-header ANSI C immediate mode cross-platform GUI library
Cool little library, I'm using it, but author has an ego the size of Wolfram's. This is just one snippet, there are many if you rummage through the docs and issues: > In the 1970s, programming was an elite's task. Today programming is done by uneducated "farmers" and as a result, the care for smart algorithms, memory usage, CPU-time usage and the like has dwindled in comparison. https://github.com/uNetworking/uWebSockets/blob/master/misc/...
In uWebSockets
Lots of reasons: - Code cleanliness: their code almost looks like code golfing. Hard to debug. - Dependencies: everyone has different ways of implementing everything. some are even outdated. some even have stale bots that close legitimate but unattended issues. - Performance: fastify and uWebSockets.js beats express.js on benchmarks. see https://www.fastify.io/benchmarks/ and https://github.com/uNetworking/uWebSockets/tree/master/bench... - Multi-part parsing: this is built-in with uWebSockets.js. on express your options are multer or busboy. - WebSocket Server support: this is built-in with uWebSockets.js. on express your options are using ws and socket.io. - WebSocket pub/sub: built-in with uWebSockets.js There are better alternatives like the following: - https://www.fastify.io/ - https://github.com/uNetworking/uWebSockets.js - https:/
Read the rest
In Ask HN: So, what's up with Phoenix (web framework)?
Couple thoughts - Savings in bandwidth might be only noticeable if the demand for scale is real and you have already exhausted other optimizations available. Think of trade-offs, the performance gains might be there, but other factors count like how familiar is your team with it, how flexible or constricting it is, etc etc. - WebSockets are easier to implement on the client-side, most developers are familiar with it, both in web app and mobile apps. - Since WebSockets are bi-directional, it's easy to let client send any data (e.g. for debugging, tracing, monitoring) almost effortlessly any time you might need it (maybe not now, maybe in the future). - WebSockets support binary data, you can use existing serialization formats like msgpack, or have your own binary serialization format. - There are WebSocket web frameworks out there like uWe
Read the rest
bSockets (written in C & C++, has Node.js API), used by most trading platforms, which got better performance than most web frameworks out there. - https://github.com/uNetworking/uWebSockets - https://github.com/uNetworking/uWebSockets.js/ - https://github.com/uNetworking/uWebSockets/tree/master/bench...
In Ask HN: Any one with experience with Server Sent Event at scale?

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.