Apache HTTP Server vs Payara

Overview

Apache HTTP Server

Stacks64.5K

Followers22.8K

Votes1.4K

GitHub Stars3.8K

Forks1.2K

Payara

Stacks41

Followers73

Votes0

GitHub Stars903

Forks312

Apache HTTP Server vs Payara: What are the differences?

Introduction: Apache HTTP Server and Payara are both popular web server solutions used in web development. However, there are key differences between the two that developers should be aware of when choosing the right solution for their projects.

1. Platform Compatibility: Apache HTTP Server is compatible with various operating systems such as Windows, Linux, and Unix, while Payara is specifically designed to work best with Java applications and is compatible with Java EE and Jakarta EE specifications. This makes Payara a more specialized and tailored solution for Java-based projects.

2. Features and Functionality: Apache HTTP Server primarily focuses on serving static content and HTML files, while Payara offers more advanced features like clustering, load balancing, and support for JavaServer Pages (JSP) and Enterprise JavaBeans (EJBs). Payara's extensive feature set makes it a robust choice for complex enterprise applications.

3. Support and Community: Apache HTTP Server has a large and active open-source community, providing a wealth of resources and support forums for users. On the other hand, Payara offers commercial support and services for enterprise users, ensuring professional assistance and maintenance for critical applications. This difference in support options can be a deciding factor for organizations with specific needs.

4. Deployment and Configuration: Apache HTTP Server is known for its ease of deployment and simple configuration setup, making it a popular choice for beginners and small projects. In contrast, Payara requires a more involved setup process due to its Java EE specifications and advanced features, which may require a higher level of expertise and experience to configure properly.

5. Performance and Scalability: Apache HTTP Server is highly regarded for its performance and scalability, making it a reliable choice for high-traffic websites and applications. Payara, while also capable of supporting large-scale deployments, may require additional configuration and optimization to achieve similar levels of performance as Apache in certain scenarios.

6. Integration with Java EE: Payara is specifically designed to work seamlessly with Java EE specifications and applications, providing native support for technologies like servlets, JavaServer Faces (JSF), and Java Message Service (JMS). This deep integration with Java EE makes Payara a compelling choice for developers working with Java-based enterprise applications.

In Summary, Apache HTTP Server and Payara offer distinct features and functionalities tailored to different types of web development projects, with Apache being versatile and widely compatible, while Payara focuses on Java EE specifications and advanced enterprise features.

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

Advice on Apache HTTP Server, Payara

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

configure LVM with required logical volumes, format and mount for HTTP and Tomcat servers accordingly.
Install apache and tomcat.
Generate and apply selfsigned certs to http server.
Modify default ports on Tomcat to different ports.
Create users on RHEL for application support team.
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

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

StackShare

May 29, 2019

Needs advice

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."

725k views725k

Comments

Detailed Comparison

Apache HTTP Server	Payara
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.	It Server is a drop in replacement for GlassFish Server Open Source Edition with quarterly releases containing enhancements, bug fixes and patches.
-	Full Web Based Administration Console; Fully Scriptable Command Line Interface; Full REST-based Management Console; Fully Instrumented via JMX; Supports Rolling Upgrades of Java EE Applications
Statistics
GitHub Stars 3.8K	GitHub Stars 903
GitHub Forks 1.2K	GitHub Forks 312
Stacks 64.5K	Stacks 41
Followers 22.8K	Followers 73
Votes 1.4K	Votes 0
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	No community feedback yet
Integrations
No integrations available	CentOS Oracle Windows Ubuntu

What are some alternatives to Apache HTTP Server, Payara?

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.

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.

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

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

Apache HTTP Server vs Payara: What are the differences?

Apache HTTP Server vs Payara

Overview