soketi VS µWebSockets

In today's article we will focus on one of my favorite trios, we will use the Next.js framework to build the web application, Drizzle to define the database schema and interact with it and perhaps the most important component of this article, Soketi.

Why you’ll love VenturSeed: • We are growing • Get to work with a global team • We all get along really well and have a fun company culture • We offer opportunities for growth https://github.com/soketi/soketi

Did you consider something like Soketi?

I have not used it, but listed Soketi for a while now, to test in the next project where I need a solution like this: https://soketi.app

you can use soketi : https://soketi.app/

Pusher protocol compliant websocket notification server https://soketi.app

Soketi on cloudflare workers should be a nice alternative -> https://soketi.app

They use (uWebSockets)[https://github.com/uNetworking/uWebSockets], which was written in C++, but has an interface to use in NodeJS. It's been really performant for me in my simple tests compared to other popular websocket libs that slow down fairly quickly.

µWebSockets, pronounced as "microWebSocket”, is a WebSocket library written in C++ and has Node.js bindings. Its design focuses on being efficient and scalable, making it ideal for applications that require high concurrency and low latency.

You can do that with any single threaded library that leaves threading to you. Like for example https://github.com/uNetworking/uWebSockets

Websockets are also pretty valuable for updating the page in real time, there are servers in many languages. I'm a big fan of https://github.com/uNetworking/uWebSockets which is C++ but also has JS bindings to use with Node.js.

Can you include uWebsockets? https://github.com/uNetworking/uWebSockets

μWebSockets Génial, rapide, peut transformer l’eau en vin. Nécessite C++17.

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, 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

Really cool i also made and CAPI for using WebSocket in C, https://github.com/uNetworking/uWebSockets/tree/master/capi

I will take a deep look on your project thanks for sharing!

We discover a really fast, small, and well maintained C++ Library called uNetworking/uWebSockets, but no C API available, so we create and adapt the full C API from uNetworking/uWebSockets and will integrate libuv powered fetch and file IO, this same C API is used by Bun