LiteSpeed Web Server
Our lightweight Apache alternative conserves resources without sacrificing performance, security, compatibility, or convenience. Double the maximum capacity of your current Apache servers with LiteSpeed Web Server's streamlined event-driven architecture, capable of handling thousands of concurrent clients with minimal memory consumption and CPU usage. Protect your servers with already familiar ModSecurity rules while also taking advantage of a host of built-in anti-DDoS features, such as bandwidth and connection throttling. Conserve capital by reducing the number of servers needed to support your growing hosting business or online application. Reduce complexity by eliminating the need for an HTTPS reverse proxy or additional 3rd party caching layers. LiteSpeed Web Server is compatible with all popular Apache features including its Rewrite Engine and ModSecurity, and can load Apache configuration files directly.
Learn more
Node.js
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.
Learn more
Eclipse Jetty
Jetty provides a web server and servlet container, additionally providing support for HTTP/2, WebSocket, OSGi, JMX, JNDI, JAAS and many other integrations. These components are open source and are freely available for commercial use and distribution. Jetty is used in a wide variety of projects and products, both in development and production. Jetty has long been loved by developers due to its long history of being easily embedded in devices, tools, frameworks, application servers, and modern cloud services. Full-featured and standards-based. Open source and commercially usable, flexible and extensible, small footprint, embeddable, asynchronous, enterprise scalable, and dual-licensed under Apache and Eclipse. Large clusters, such as Facebook Presto. Cloud computing, such as Google AppEngine. With the direction of Java and the JakartaEE project (formerly JavaEE) in 2020, the current recommended version of Jetty for use depends upon the servlet API version, desired licensing, etc.
Learn more
Tornado Web Server
Tornado is a Python web framework and asynchronous networking library, originally developed at FriendFeed. By using non-blocking network I/O, Tornado can scale to tens of thousands of open connections, making it ideal for long polling, WebSockets, and other applications that require a long-lived connection to each user. Tornado is different from most Python web frameworks. It is not based on WSGI, and it is typically run with only one thread per process. While some support of WSGI is available in the tornado.wsgi module, it is not a focus of development and most applications should be written to use Tornado’s own interfaces (such as tornado.web) directly instead of using WSGI. In general, Tornado code is not thread-safe. Tornado is integrated with the standard library asyncio module and shares the same event loop (by default since Tornado 5.0). In general, libraries designed for use with asyncio can be mixed freely with Tornado.
Learn more