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. Keepalived vs nginx

Keepalived vs nginx

OverviewDecisionsComparisonAlternatives

Overview

NGINX
NGINX
Stacks115.0K
Followers61.9K
Votes5.5K
GitHub Stars28.4K
Forks7.6K
Keepalived
Keepalived
Stacks36
Followers59
Votes6

Keepalived vs nginx: What are the differences?

<Write Introduction here>
  1. Configuration: Keepalived is primarily used for high availability solutions with Its main function being to monitor the health of servers and switches, ensuring uptime for critical services. On the other hand, Nginx is a web server and reverse proxy that focuses on efficiently serving web content and managing HTTP traffic.

  2. Load Balancing: Keepalived supports both Layer 4 (TCP/UDP) and Layer 7 (HTTP) load balancing, making it suitable for a wider range of applications. Nginx, however, excels in Layer 7 load balancing, providing advanced features for routing traffic based on various criteria.

  3. Monitoring: Keepalived offers extensive monitoring capabilities for server health and service availability, enabling automatic failover and maintaining high service uptime. Nginx, while able to handle a large number of concurrent connections efficiently, lacks native support for comprehensive server monitoring and failover mechanisms.

  4. High Availability Features: Keepalived specializes in providing high availability solutions through techniques like VRRP (Virtual Router Redundancy Protocol) and VSMTP, ensuring services remain online even in the event of server failures. Nginx, although capable of handling high traffic loads, does not inherently provide the same level of automatic failover and redundancy features.

  5. Application Support: Keepalived is commonly used for critical network services such as DNS, email, and database servers that require continuous availability. Nginx, on the other hand, is widely used for web applications, caching, and as a reverse proxy for HTTP servers, catering more to web-specific needs.

  6. Scalability: Keepalived can be scaled horizontally by adding more instances to distribute the workload and improve fault tolerance, ensuring high availability across multiple nodes. In contrast, Nginx helps in scaling web applications by efficiently handling concurrent connections and distributing traffic, but its focus remains more on web server functionalities rather than high availability scaling.

In Summary, Keepalived and Nginx differ in their focus on high availability solutions for network services and efficient web traffic management, respectively, with variations in load balancing capabilities, monitoring features, and application 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 NGINX, Keepalived

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
jlp78
jlp78

May 31, 2019

ReviewonNGINXNGINX

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.

727k views727k
Comments
StackShare
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

NGINX
NGINX
Keepalived
Keepalived

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.

The main goal of this project is to provide simple and robust facilities for loadbalancing and high-availability to Linux system and Linux based infrastructures.

-
High availability; Job Scheduling,
Statistics
GitHub Stars
28.4K
GitHub Stars
-
GitHub Forks
7.6K
GitHub Forks
-
Stacks
115.0K
Stacks
36
Followers
61.9K
Followers
59
Votes
5.5K
Votes
6
Pros & Cons
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
  • 2
    Extremely fast (IPVS)
  • 2
    Load Balancer
  • 1
    Virtual IP HA with VRRP
  • 1
    2 nodes HA cluster management
Integrations
No integrations available
Linux
Linux
HAProxy
HAProxy

What are some alternatives to NGINX, Keepalived?

Apache HTTP Server

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

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.

Consul

Consul

Consul is a tool for service discovery and configuration. Consul is distributed, highly available, and extremely scalable.

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.

Eureka

Eureka

Eureka is a REST (Representational State Transfer) based service that is primarily used in the AWS cloud for locating services for the purpose of load balancing and failover of middle-tier servers.

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.

Zookeeper

Zookeeper

A centralized service for maintaining configuration information, naming, providing distributed synchronization, and providing group services. All of these kinds of services are used in some form or another by distributed applications.

Related Comparisons

GitHub
Bitbucket

Bitbucket vs GitHub vs GitLab

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