-
-
hyper-express
High performance Node.js webserver with a simple-to-use API powered by uWebsockets.js under the hood.
-
SurveyJS
Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.
-
Check this Node.js multitheaded backend with benchmarks: https://github.com/elestio/cloudgate-app
NodeJS is plenty fast, If not one of the fastest backend languages out there given you write proper code and follow proper guidelines. Majority of the people that post the "NodeJs or Javascript is too slow" posts simply do not understand the language well enough to write proper code that provides high performance. While Javascript is single threaded, that does not mean Javascript is slow, that just means that you have to write code that does not block the event loop (aka thread/core) and can scale over multiple cores easily by being stateless whenever possible. NodeJs will not outperform the likes of C++ when it comes to CPU intensive tasks such as encryption or compression. However, you do have the ability to write or use C++ bindings in your NodeJs application which can solve the problem above. If you want an example of extreme performance in NodeJs, See my webserver package https://github.com/kartikk221/hyper-express which outperforms many other webservers in go, rust, nim, java, cpp etc.
Here is a large collection of webserver benchmarks. https://github.com/the-benchmarker/web-frameworks & https://web-frameworks-benchmark.netlify.app/result . You can use nanoexpress (Another webserver package based on uWebsockets.js) as a reference to measure HyperExpress's performance and compare it to other frameworks from various languages. The benchmarks you have linked seems to be inaccurate and outdated. A million requests/second for a single machine is very hard to maintain simply because the network upload/download speed/adapter for any cloud provider instance would not suppor the amount of data being transported. You can notice in the benchmarks on the HyperExpress Github, uWebsockets.js/HyperExpress clock in a 400ms+ average response latency while serving almost 200k requests/second. This is because the network speed of the Vultr instance becomes the bottleneck.