Uvicorn vs lighttpd

Overview

lighttpd

Stacks156

Followers133

Votes27

Uvicorn

Stacks170

Followers119

Votes0

Uvicorn vs lighttpd: What are the differences?

Server Type: Uvicorn is an ASGI server that runs Python web applications, while lighttpd is a lightweight and efficient web server that supports a variety of programming languages.
Concurrency Model: Uvicorn uses an asynchronous concurrency model, enabling it to handle multiple requests concurrently without blocking, while lighttpd uses a traditional threaded or event-driven concurrency model.
Ease of Configuration: Uvicorn allows for easy configuration through command-line arguments or a configuration file, making it convenient to set up and customize, whereas lighttpd typically requires manual configuration of its configuration file, making it less user-friendly for beginners.
TLS/SSL Support: Uvicorn does not natively support TLS/SSL encryption, so an additional reverse proxy server or middleware is needed to handle secure connections, whereas lighttpd includes built-in support for TLS/SSL, allowing it to handle secure connections without the need for external components.
Performance: Uvicorn is known for its high performance and scalability, as it is optimized for handling a large number of concurrent connections, while lighttpd is also efficient and lightweight but may not be as performant in certain scenarios.
Supported Platforms: Uvicorn is compatible with various operating systems and platforms, including Windows, Linux, and macOS, while lighttpd is primarily designed for Unix-like systems, with limited or experimental support for other platforms.

In summary, Uvicorn is an ASGI server with an asynchronous concurrency model, while lighttpd is a lightweight web server that supports various programming languages. Uvicorn has easier configuration, requires additional components for TLS/SSL support, and excels in performance and platform compatibility.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs

CLI (Node.js)

Manual

Detailed Comparison

lighttpd	Uvicorn
lighttpd has a very low memory footprint compared to other webservers and takes care of cpu-load. Its advanced feature-set (FastCGI, CGI, Auth, Output-Compression, URL-Rewriting and many more) make lighttpd the perfect webserver-software for every server that suffers load problems.	It is a lightning-fast ASGI server, built on uvloop and httptools. Until recently Python has lacked a minimal low-level server/application interface for asyncio frameworks. The ASGI specification fills this gap, and means we're now able to start building a common set of tooling usable across all asyncio frameworks.
-	ASGI server implementation; Supports HTTP/1.1 and WebSockets; Support for HTTP/2 is planned
Statistics
Stacks 156	Stacks 170
Followers 133	Followers 119
Votes 27	Votes 0
Pros & Cons
Pros 7 Lightweight 6 Easy setup 2 Proxy 2 Virtal hosting 2 Simplicity	No community feedback yet
Integrations
No integrations available	Python

What are some alternatives to lighttpd, Uvicorn?

NGINX

nginx [engine x] is an HTTP and reverse proxy server, as well as a mail proxy server, written by Igor Sysoev. According to Netcraft nginx served or proxied 30.46% of the top million busiest sites in Jan 2018.

Apache HTTP Server

The Apache HTTP Server is a powerful and flexible HTTP/1.1 compliant web server. Originally designed as a replacement for the NCSA HTTP Server, it has grown to be the most popular web server on the Internet.

Unicorn

Unicorn is an HTTP server for Rack applications designed to only serve fast clients on low-latency, high-bandwidth connections and take advantage of features in Unix/Unix-like kernels. Slow clients should only be served by placing a reverse proxy capable of fully buffering both the the request and response in between Unicorn and slow clients.

Microsoft IIS

Internet Information Services (IIS) for Windows Server is a flexible, secure and manageable Web server for hosting anything on the Web. From media streaming to web applications, IIS's scalable and open architecture is ready to handle the most demanding tasks.

Apache Tomcat

Apache Tomcat powers numerous large-scale, mission-critical web applications across a diverse range of industries and organizations.

Passenger

Phusion Passenger is a web server and application server, designed to be fast, robust and lightweight. It takes a lot of complexity out of deploying web apps, adds powerful enterprise-grade features that are useful in production, and makes administration much easier and less complex.

Gunicorn

Gunicorn is a pre-fork worker model ported from Ruby's Unicorn project. The Gunicorn server is broadly compatible with various web frameworks, simply implemented, light on server resources, and fairly speedy.

Jetty

Jetty is used in a wide variety of projects and products, both in development and production. Jetty can be easily embedded in devices, tools, frameworks, application servers, and clusters. See the Jetty Powered page for more uses of Jetty.

Swoole

It is an open source high-performance network framework using an event-driven, asynchronous, non-blocking I/O model which makes it scalable and efficient.

Puma

Unlike other Ruby Webservers, Puma was built for speed and parallelism. Puma is a small library that provides a very fast and concurrent HTTP 1.1 server for Ruby web applications.

Related Comparisons

Uvicorn vs lighttpd: What are the differences?

Server Type: Uvicorn is an ASGI server that runs Python web applications, while lighttpd is a lightweight and efficient web server that supports a variety of programming languages.
Concurrency Model: Uvicorn uses an asynchronous concurrency model, enabling it to handle multiple requests concurrently without blocking, while lighttpd uses a traditional threaded or event-driven concurrency model.
Ease of Configuration: Uvicorn allows for easy configuration through command-line arguments or a configuration file, making it convenient to set up and customize, whereas lighttpd typically requires manual configuration of its configuration file, making it less user-friendly for beginners.
TLS/SSL Support: Uvicorn does not natively support TLS/SSL encryption, so an additional reverse proxy server or middleware is needed to handle secure connections, whereas lighttpd includes built-in support for TLS/SSL, allowing it to handle secure connections without the need for external components.
Performance: Uvicorn is known for its high performance and scalability, as it is optimized for handling a large number of concurrent connections, while lighttpd is also efficient and lightweight but may not be as performant in certain scenarios.
Supported Platforms: Uvicorn is compatible with various operating systems and platforms, including Windows, Linux, and macOS, while lighttpd is primarily designed for Unix-like systems, with limited or experimental support for other platforms.

Uvicorn vs lighttpd

Overview