Kestrel vs. MacHTTP-js vs. Node.js vs. django-mysql Comparison Chart

Kestrel is a cross-platform web server for ASP.NET Core. Kestrel is the web server that's included and enabled by default in ASP.NET Core project templates. Kestrel supports HTTPS, HTTP/2 (except on macOS), Opaque upgrade used to enable WebSockets, Unix sockets for high performance behind Nginx. Kestrel is supported on all platforms and versions that .NET Core supports. Some browsers require granting explicit permission to trust the local development certificate. Project templates configure apps to run on HTTPS by default and include HTTPS redirection and HSTS support. The Kestrel web server has constraint configuration options that are especially useful in Internet-facing deployments. There's a separate limit for connections that have been upgraded from HTTP or HTTPS to another protocol (for example, on a WebSockets request). The default maximum request body size is 30,000,000 bytes, which is approximately 28.6 MB.

As an asynchronous event-driven JavaScript runtime, Node.js is designed to build scalable network applications. Upon each connection, the callback is fired, but if there is no work to be done, Node.js will sleep. This is in contrast to today's more common concurrency model, in which OS threads are employed. Thread-based networking is relatively inefficient and very difficult to use. Furthermore, users of Node.js are free from worries of dead-locking the process, since there are no locks. Almost no function in Node.js directly performs I/O, so the process never blocks except when the I/O is performed using synchronous methods of Node.js standard library. Because nothing blocks, scalable systems are very reasonable to develop in Node.js. Node.js is similar in design to, and influenced by, systems like Ruby's Event Machine and Python's Twisted. Node.js takes the event model a bit further. It presents an event loop as a runtime construct instead of as a library.