Apache HTTP Server vs Passenger: What are the differences?
What is Apache HTTP Server? 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.
What is Passenger? A fast and robust web server and application server for Ruby, Python and Node.js. 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.
Apache HTTP Server and Passenger can be categorized as "Web Servers" tools.
"Web server" is the top reason why over 468 developers like Apache HTTP Server, while over 43 developers mention "Nginx integration" as the leading cause for choosing Passenger.
Apache HTTP Server and Passenger are both open source tools. It seems that Passenger with 4.41K GitHub stars and 505 forks on GitHub has more adoption than Apache HTTP Server with 2.21K GitHub stars and 657 GitHub forks.
According to the StackShare community, Apache HTTP Server has a broader approval, being mentioned in 6194 company stacks & 1067 developers stacks; compared to Passenger, which is listed in 380 company stacks and 40 developer stacks.
What is Apache HTTP Server?
What is Passenger?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Apache HTTP Server?
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
We use httpd in front of our Tomcat web server. Apache terminates the TLS connections and forwards to the embedded Tomcat server(s) for request processing. We also use it as load balancer for multi-server deployments.
Most known webserver. We are using Apache due to his htaccess feature but its just a backedn to proccess PHP. In font of Apache we are using NGINX to server static files
Apache splits static traffic from application traffic, as well as providing a selection of tools to assist in running of the site (rewrites, logging etc).
Primary web server, delivers PHP-rendered pages as well as static HTML content. Ruby CGIs deliver objects to browser-side code using REST/JSON
modproxybalancer provides highly concurrent end-user browser connections, and manages session routing to the application cluster
"deploy + forget" application deployment with good default configuration.