Apache HTTP Server vs Jetty

Need advice about which tool to choose?Ask the StackShare community!

Apache HTTP Server

62.1K
20.6K
+ 1
1.4K
Jetty

408
290
+ 1
43
Add tool

Apache HTTP Server vs Jetty: What are the differences?

Developers describe Apache HTTP Server as "The most popular web server on the Internet since April 1996". 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. On the other hand, Jetty is detailed as "An open-source project providing an HTTP server, HTTP client, and javax.servlet container". 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.

Apache HTTP Server and Jetty can be categorized as "Web Servers" tools.

"Web server" is the primary reason why developers consider Apache HTTP Server over the competitors, whereas "Lightweight" was stated as the key factor in picking Jetty.

Apache HTTP Server and Jetty are both open source tools. Jetty with 2.55K GitHub stars and 1.4K forks on GitHub appears to be more popular than Apache HTTP Server with 2.21K GitHub stars and 657 GitHub forks.

Intuit, HotelTonight, and Keen are some of the popular companies that use Apache HTTP Server, whereas Jetty is used by Conceptboard, Cask, and Eyereturn Marketing. Apache HTTP Server has a broader approval, being mentioned in 6194 company stacks & 1067 developers stacks; compared to Jetty, which is listed in 58 company stacks and 16 developer stacks.

Advice on Apache HTTP Server and Jetty

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!

See more
Replies (1)
Simon Aronsson
Developer Advocate at k6 / Load Impact · | 4 upvotes · 404.3K views
Recommends
NGINXNGINX

I would pick nginx over both IIS and Apace HTTP Server any day. Combine it with docker, and as you grow maybe even traefik, and you'll have a really flexible solution for serving http content where you can take sites and projects up and down without effort, easily move it between systems and dont have to handle any dependencies on your actual local machine.

See more
Needs advice
on
Apache HTTP ServerApache HTTP Server
and
NGINXNGINX

From a StackShare Community member: "We are a LAMP shop currently focused on improving web performance for our customers. We have made many front-end optimizations and now we are considering replacing Apache with nginx. I was wondering if others saw a noticeable performance gain or any other benefits by switching."

See more
Replies (3)
Recommends
NGINXNGINX

I use nginx because it is very light weight. Where Apache tries to include everything in the web server, nginx opts to have external programs/facilities take care of that so the web server can focus on efficiently serving web pages. While this can seem inefficient, it limits the number of new bugs found in the web server, which is the element that faces the client most directly.

See more
Leandro Barral
Recommends
NGINXNGINX

I use nginx because its more flexible and easy to configure

See more
Christian Cwienk
Software Developer at SAP · | 1 upvotes · 384.3K views

I use Apache HTTP Server because it's intuitive, comprehensive, well-documented, and just works

See more
Decisions about Apache HTTP Server and Jetty
Daniel Calvo
Co-Founder at Polpo Data Analytics & Software Development · | 8 upvotes · 107.7K views

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.

See more
Grant Steuart
  • Server rendered HTML output from PHP is being migrated to the client as Vue.js components, future plans to provide additional content, and other new miscellaneous features all result in a substantial increase of static files needing to be served from the server. NGINX has better performance than Apache for serving static content.
  • The change to NGINX will require switching from PHP to PHP-FPM resulting in a distributed architecture with a higher complexity configuration, but this is outweighed by PHP-FPM being faster than PHP for processing requests.
  • The NGINX + PHP-FPM setup now allows for horizontally scaling of resources rather vertically scaling the previously combined Apache + PHP resources.
  • PHP shell tasks can now efficiently be decoupled from the application reducing main application footprint and allow for scaling of tasks on an individual basis.
See more

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.

See more
Get Advice from developers at your company using StackShare Enterprise. Sign up for StackShare Enterprise.
Learn More
Pros of Apache HTTP Server
Pros of Jetty
  • 478
    Web server
  • 305
    Most widely-used web server
  • 218
    Virtual hosting
  • 148
    Fast
  • 138
    Ssl support
  • 45
    Since 1996
  • 28
    Asynchronous
  • 5
    Robust
  • 4
    Proven over many years
  • 1
    Mature
  • 1
    Perfect Support
  • 1
    Perfomance
  • 0
    Many available modules
  • 0
    Many available modules
  • 14
    Lightweight
  • 10
    Very fast
  • 9
    Embeddable
  • 5
    Scalable
  • 5
    Very thin

Sign up to add or upvote prosMake informed product decisions

Cons of Apache HTTP Server
Cons of Jetty
  • 3
    Hard to set up
  • 0
    Student

Sign up to add or upvote consMake informed product decisions

What is 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.

What is 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.

Need advice about which tool to choose?Ask the StackShare community!

Jobs that mention Apache HTTP Server and Jetty as a desired skillset
CBRE
United States of America Texas Richardson
CBRE
United States of America Texas Richardson
Pinterest
San Francisco, CA, US; Palo Alto, CA, US; Seattle, WA, US;
Pinterest
San Francisco, CA, US; Palo Alto, CA, US; Seattle, WA, USA
What companies use Apache HTTP Server?
What companies use Jetty?
See which teams inside your own company are using Apache HTTP Server or Jetty.
Sign up for StackShare EnterpriseLearn More

Sign up to get full access to all the companiesMake informed product decisions

What tools integrate with Apache HTTP Server?
What tools integrate with Jetty?

Sign up to get full access to all the tool integrationsMake informed product decisions

Blog Posts

What are some alternatives to Apache HTTP Server and Jetty?
Apache Tomcat
Apache Tomcat powers numerous large-scale, mission-critical web applications across a diverse range of industries and organizations.
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.
JBoss
An application platform for hosting your apps that provides an innovative modular, cloud-ready architecture, powerful management and automation, and world class developer productivity.
XAMPP
It consists mainly of the Apache HTTP Server, MariaDB database, and interpreters for scripts written in the PHP and Perl programming languages.
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.
See all alternatives