hyper-express

Yeah I’m personally of the opinion that the performance loss for regular web services is worth it 99% of the time. RAM is cheap, human time is not. That said I definitely believe your characterization of resource hunger between nginx and traefik. You are the second person to mention using websockets for requests in as many days… How do you deal with scale out? Sticky cookie routing seems like almost a requirement if you don’t want to deploy a redis-alike. Also just out of curiosity, do you use hyper-express[0]? [0]: https://github.com/kartikk221/hyper-express

I’m a fan of hyper-express, built on top of uWebSockets with an api similar to express - https://github.com/kartikk221/hyper-express

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:/

Great experience with it. The examples in the repo, the issues and discussions sections, and the documentations are all very helpful. Alex and the other users are also quite hands-on in replying on each and every issue and discussion there. We have some thin wrapper for uWebSockets.js that lets us do the following: - parse request json - parse request multipart data - serve response json - serve response buffers - serve response streams - serve response static files - support async handler - support multiple async handlers (middlewares) links are here - https://github.com/joshxyzhimself/modules/blob/main/uwu.mjs - https://github.com/joshxyzhimself/modules/blob/main/uwu.d.ts - https://github.com/joshxyzhimself/modules/blob/main/uwu.test... internally we just serve http, then it goes through caddy or haproxy depending on the project's needs

maybe it's bottlenecked on Node's built-in http module, there are projects like uWebSockets.js (and hyper-express [1] built on top of it) [1] which show a 10x increase in throughput. [1] https://github.com/kartikk221/hyper-express/blob/master/docs...