What is Traefik?
Who uses Traefik?
Here are some stack decisions, common use cases and reviews by companies and developers who chose Traefik in their tech stack.
We switched to Traefik so we can use the REST API to dynamically configure subdomains and have the ability to redirect between multiple servers.
We still use nginx with a docker-compose to expose the traffic from our APIs and TCP microservices, but for managing routing to the internet Traefik does a much better job
To simplify development and deployment, we decided to use Docker to build our application images, Docker Compose to orchestrate our production containers, and Traefik to bind everything together.
Docker is a great tool since it allows us to make our backend app platform-agnostic. This allows us to migrate our infrastructure from one platform to another without much effort.
Docker Compose lets us define our services and how they connect to each other easily. The ability to have an outline of our services and have our containers managed automatically greatly benefits us and removes lots of manual effort on our developers' part.
While we initially used Nginx to route our traffic, we were tired of having to manually set up all of our configuration. So we decided to move to Traefik so that our containers are automatically routed and load-balanced, without any additional configuration. If we do need additional configuration, we are able to easily add the configuration in our Docker Compose files, rather than in some weird config file in /etc/
Traefik is used by our DevOps team to manage the network in our infrastructure, inside Kubernetes.
- Continuously updates its configuration (No restarts!)
- Supports multiple load balancing algorithms
- Provides HTTPS to your microservices by leveraging Let's Encrypt (wildcard certificates support)
- Circuit breakers, retry
- High Availability with cluster mode
- See the magic through its clean web UI
- Websocket, HTTP/2, GRPC ready
- Provides metrics
- Keeps access logs
- Exposes a Rest API