nginx vs HAProxy

LB choice.

Overview

nginx and HAProxy are two long-standing load balancers with different design centres. nginx is a web server that also load-balances (rich HTTP feature set, static-file serving, reverse-proxy plus LB in one); HAProxy is a pure load balancer (deeper traffic-management primitives, more advanced health checks, lower memory footprint). The right answer depends on whether the workload needs combined web-server-plus-LB or focused LB.

• nginx: web server plus LB. HTTP feature richness, static-file serving, reverse-proxy plus LB in one binary. Default when one process serves both roles.
• HAProxy: pure load balancer. Deeper traffic-management primitives, advanced health checks, lower memory. Default when LB is the only role.
• Operational fit per team. Existing nginx config inheritance biases toward nginx; teams that want a focused LB tool bias toward HAProxy.
• Per-tier choice. Edge tier vs internal LB tier may pick differently. Document the rationale per tier.

The approach

Workload-driven choice, per-team operational fit considered, documented rationale per tier. The discipline is making the LB choice once with a written reason rather than running both tools at the same tier.

• Workload-driven. LB per tier. Reality drives the answer.
• nginx for web server plus LB. One process serves static, reverse-proxy, and LB roles. Default when consolidation matters.
• HAProxy for pure LB. Edge LB or internal LB tier where focused traffic management is the requirement.
• Operational fit plus documented rationale. Team workflow considered; per-tier rationale captured. Future migrations have a paper trail.

Why this compounds

The right LB choice compounds across years. Config patterns and team expertise align with the tool; cross-tier tooling (health-check templates, observability, deploy automation) gets built once and reused. By year two the LB choice is automatic per tier.

• Better operational fit. LB matches team and tier. Velocity stays high.
• Workload-driven decisions. Replaces tribal preference with documented rationale. Quality of choice improves.
• Better operational reliability. Right LB means health checks behave predictably. Incident MTTR drops.
• Year-one investment, year-two habit. First LB choice is the investment; subsequent tiers inherit the patterns.