Introduction to Traefik

What is Traefik?

Traefik (pronounced "traffic") is an open-source Application Proxy that handles routing, load balancing, and service discovery for your microservices and containers. It was created by Emile Vauge in 2015 and is written in Go.

Unlike traditional reverse proxies (nginx, HAProxy, Apache) that require manual configuration files and reloads, Traefik automatically discovers services by watching your infrastructure—Docker containers, Kubernetes pods, Consul services, and more.

Why Traefik?

Automatic Service Discovery

Traefik integrates directly with your infrastructure providers. When you deploy a new container with the right labels, Traefik immediately knows how to route traffic to it.

Dynamic Configuration

Routes, middlewares, and certificates update in real-time—no reloads, no downtime.

Built-in Let's Encrypt

TLS certificates are automatically obtained and renewed via ACME. No more manual certbot commands.

Cloud-Native by Design

Designed for containers and orchestration: Docker, Kubernetes, Nomad, and major cloud providers.

Observability Built-In

Metrics (Prometheus, OpenTelemetry), access logs, and a web dashboard come out of the box.

Middleware Pipeline

Chain 30+ built-in middleware modules (rate limiting, authentication, headers, retries, circuit breakers) without writing any code.

Core Concepts

Traefik's configuration model revolves around four core components:

1. EntryPoints — The network ports Traefik listens on (e.g. :80 for HTTP, :443 for HTTPS)
2. Routers — Rules that match incoming requests and route them to the right service
3. Services — The backend destinations (load balanced pools of servers)
4. Middlewares — Request/response transformations chained between routers and services

Traefik vs Alternatives

When to Use Traefik

Traefik excels when:

• You run containers (Docker, Kubernetes, Nomad)
• You want automatic TLS with Let's Encrypt
• You need dynamic reconfiguration without downtime
• You want built-in observability
• Your architecture uses microservices or APIs

Traefik may not be ideal when:

• You need a pure static file server (nginx is simpler)
• You have extremely simple routing needs
• You require advanced nginx-specific features (like njs scripting)

The Traefik Ecosystem

Traefik is part of a broader ecosystem under Traefik Labs:

• Traefik Proxy — The open-source reverse proxy (v3.x is current)
• Traefik Hub — Commercial API management and connectivity platform built on Traefik Proxy
• Traefik Enterprise — Commercial version with additional security and compliance features
• Traefik AI Gateway — AI-specific gateway for managing LLM API traffic
• Traefik MCP Gateway — Model Context Protocol gateway for AI agent communication

Getting Started

To install Traefik:

Using Docker (recommended for beginners):

# docker-compose.yml
services:
  traefik:
    image: traefik:v3.3
    command:
      - "--api.dashboard=true"
      - "--providers.docker=true"
      - "--entrypoints.web.address=:80"
    ports:
      - "80:80"
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock

Using static binary:

# Linux
curl -L https://github.com/traefik/traefik/releases/download/v3.3.0/traefik_v3.3.0_linux_amd64.tar.gz | tar xz
sudo mv traefik /usr/local/bin/
traefik --configFile=traefik.yml