StackShareStackShare
Follow on
StackShare

Discover and share technology stacks from companies around the world.

Follow on

© 2025 StackShare. All rights reserved.

Product

  • Stacks
  • Tools
  • Feed

Company

  • About
  • Contact

Legal

  • Privacy Policy
  • Terms of Service
  1. Stackups
  2. Application & Data
  3. Platform as a Service
  4. Web Servers
  5. Apache HTTP Server vs Cherokee vs nginx

Apache HTTP Server vs Cherokee vs nginx

OverviewDecisionsComparisonAlternatives

Overview

Apache HTTP Server
Apache HTTP Server
Stacks64.5K
Followers22.8K
Votes1.4K
GitHub Stars3.8K
Forks1.2K
NGINX
NGINX
Stacks115.0K
Followers61.9K
Votes5.5K
GitHub Stars28.4K
Forks7.6K
Cherokee
Cherokee
Stacks4
Followers26
Votes4

Apache HTTP Server vs Cherokee vs nginx: What are the differences?

Introduction:

Apache HTTP Server, Cherokee, and Nginx are all popular web servers used to serve static and dynamic content over the internet. While they perform similar functions, there are key differences that differentiate them from each other.

  1. Configuration Files: Apache HTTP Server uses a single monolithic configuration file (httpd.conf) which can become complex and difficult to manage, while Cherokee uses an XML-based configuration file that is more structured and easier to understand. Nginx follows a modular approach with separate configuration files for different aspects like server blocks, upstream servers, and locations, making it more flexible and scalable.

  2. Resource Usage: Nginx is known for its low resource usage and high performance, making it a preferred choice for high-traffic websites or applications. Cherokee also has a reputation for being lightweight, using architecture designed for high efficiency. On the other hand, Apache HTTP Server may consume more resources due to its process-based architecture.

  3. Module Support: Apache HTTP Server has a vast library of modules available for various functionalities, while Nginx has a more limited set of modules but focuses on performance-critical features. Cherokee also has a range of modules but may not have the extensive support and community that Apache enjoys.

  4. Reverse Proxy Capabilities: Nginx is widely recognized for its reverse proxy capabilities and is often used in front of application servers to improve performance and handle incoming requests. Apache HTTP Server and Cherokee also have reverse proxy features, but Nginx is considered to excel in this area due to its high concurrency and low memory usage.

  5. Ease of Scalability: Nginx is built with scalability in mind, allowing it to effectively handle a large number of concurrent connections with minimal resources. Apache HTTP Server and Cherokee can also scale, but may require more configuration and fine-tuning to achieve similar levels of performance under high loads.

  6. Community Support: Apache HTTP Server has a large and active community with a wealth of documentation, tutorials, and forums for support. Nginx also has a strong community backing with frequent updates and enhancements. Cherokee, while having a smaller user base, still offers community support through forums and documentation.

In Summary, Apache HTTP Server, Cherokee, and Nginx each have their unique strengths in terms of configuration, resource usage, module support, reverse proxy capabilities, scalability, and community support.

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)
or
Manual

Advice on Apache HTTP Server, NGINX, Cherokee

Daniel
Daniel

Co-Founder at Polpo Data Analytics & Software Development

May 25, 2021

Decided

For us, NGINX is a lite HTTP server easy to configure. On our research, we found a well-documented software we a lot of support from the community.

We have been using it alongside tools like certbot and it has been a total success.

We can easily configure our sites and have a folder for available vs enabled sites, and with the nginx -t command we can easily check everything is running fine.

289k views289k
Comments
Hari
Hari

Mar 3, 2020

Needs advice

I was in a situation where I have to configure 40 RHEL servers 20 each for Apache HTTP Server and Tomcat server. My task was to

  1. configure LVM with required logical volumes, format and mount for HTTP and Tomcat servers accordingly.
  2. Install apache and tomcat.
  3. Generate and apply selfsigned certs to http server.
  4. Modify default ports on Tomcat to different ports.
  5. Create users on RHEL for application support team.
  6. other administrative tasks like, start, stop and restart HTTP and Tomcat services.

I have utilized the power of ansible for all these tasks, which made it easy and manageable.

419k views419k
Comments
greg00m
greg00m

Mar 9, 2020

Needs advice

I am diving into web development, both front and back end. I feel comfortable with administration, scripting and moderate coding in bash, Python and C++, but I am also a Windows fan (i love inner conflict). What are the votes on web servers? IIS is expensive and restrictive (has Windows adoption of open source changed this?) Apache has the history but seems to be at the root of most of my Infosec issues, and I know nothing about nginx (is it too new to rely on?). And no, I don't know what I want to do on the web explicitly, but hosting and data storage (both cloud and tape) are possibilities.
Ready, aim fire!

766k views766k
Comments

Detailed Comparison

Apache HTTP Server
Apache HTTP Server
NGINX
NGINX
Cherokee
Cherokee

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.

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.

Cherokee is highly efficient, extremely lightweight and provides rock solid stability. Among its many features there is one that deserves special credit: a user friendly interface called cherokee-admin that is provided for a no-hassle configuration of every single feature of the server.

Statistics
GitHub Stars
3.8K
GitHub Stars
28.4K
GitHub Stars
-
GitHub Forks
1.2K
GitHub Forks
7.6K
GitHub Forks
-
Stacks
64.5K
Stacks
115.0K
Stacks
4
Followers
22.8K
Followers
61.9K
Followers
26
Votes
1.4K
Votes
5.5K
Votes
4
Pros & Cons
Pros
  • 479
    Web server
  • 305
    Most widely-used web server
  • 217
    Virtual hosting
  • 148
    Fast
  • 138
    Ssl support
Cons
  • 4
    Hard to set up
Pros
  • 1453
    High-performance http server
  • 895
    Performance
  • 730
    Easy to configure
  • 607
    Open source
  • 530
    Load balancer
Cons
  • 10
    Advanced features require subscription
Pros
  • 4
    The logo is cute

What are some alternatives to Apache HTTP Server, NGINX, Cherokee?

Unicorn

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

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

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

Passenger

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

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

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.

lighttpd

lighttpd

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.

Swoole

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

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.

Caddy

Caddy

Caddy 2 is a powerful, enterprise-ready, open source web server with automatic HTTPS written in Go.

Related Comparisons

Bootstrap
Materialize

Bootstrap vs Materialize

Laravel
Django

Django vs Laravel vs Node.js

Bootstrap
Foundation

Bootstrap vs Foundation vs Material UI

Node.js
Spring Boot

Node.js vs Spring-Boot

Liquibase
Flyway

Flyway vs Liquibase