Loading content
Traefik is a modern edge router and reverse proxy focused on dynamic service discovery and automatic configuration. It acts as an ingress controller for Kubernetes and provides load balancing, TLS termination, and middleware. Traefik simplifies operating microservices through native integrations and declarative configuration. It is written in Go and actively…
Use this profile to understand the building block briefly, place it in the model, and open related building blocks.
Technical building block: can be automated, integrated, or operated.
Concrete cog in the system that works inside larger relationships.
Traefik is a dynamic reverse proxy and load balancer that routes traffic to services from their current configuration.
Traefik was created by Emile Vauge as an open-source project to automate routing in dynamic container environments. The project is now continued by the Traefik Labs community and company.
Traefik watches providers such as Docker or Kubernetes, discovers services, and derives routers and rules. Incoming requests are matched by host names or paths and sent to suitable backends.
Providers expose running services and metadata to Traefik.
Rules assign requests to suitable services.
Traefik mediates between clients and backends.
Traefik simplifies routing and TLS for dynamic microservice and container environments.
Where this building block is located in the topic model.
No structure path available.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.