LoopBack VS hyper-express

Backend is usually an API you design, can simply use Rails for this, basic Express.js or some framework like https://loopback.io/ if you want javascript otherwise you want 'system design' https://github.com/donnemartin/system-design-primer for all the load balancers/dbms if that's what you mean.

LoopBack – Highly Extensible Node.js and TypeScript framework

We deliberately decided not to use "kitchen-sink included" frameworks such as Laravel, Django, Loopback or Nest.js to keep things simple.

Loopback

I'd say check out https://loopback.io

This interface defines the basic CRUD capabilities that any entity should provide. This contract is based on frameworks like Loopback, Django RF, RoR and Spring. The Service.kt looks something like:

Hey, I believe uWebsockets.js does support clustering. I'm the author of https://github.com/kartikk221/hyper-express which is written on top of uWebsockets.js and is pretty much the fastest webserver in Node land with an Express-like API and all of the common features such as middlewares, Router, async/sync, Websockets, Server Sent Events, File Uploading in a single package that is about same size as Express. The only catch is that you lose about 14% performance from the uWebsockets.js peak because of all the features but this is being improved and a well worth trade off for the familiar developer experience with still almost 2.5x performance of Fastify and other similar frameworks.

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

Building your own webserver on top of a lower level networking library in Node.js can be a good way to learn all 3 of those things. I have built a webserver called HyperExpress which is essentially a layer on top of a low level C++ websever called uWebsockets and I had to utilize and progress my knowledge in buffers, emitters and streams to achieve the same API as Express.js and make it usable for Node.js applications: https://github.com/kartikk221/hyper-express Feel free to dig around in the code and make any PRs for improvements!

You can check out source code here if you’d like to do more digging https://github.com/kartikk221/hyper-express

Are classes absolutely needed in JS? No, not really. Are classes really nice and significantly improve the readability/flow of your code in some cases? Sure, an example could be a webserver I wrote: https://github.com/kartikk221/hyper-express