Traefik vs Varnish: What are the differences?
Developers describe Traefik as "Load Balancer for Microservices". Træfɪk is a modern HTTP reverse proxy and load balancer made to deploy microservices with ease. It supports several backends (Docker, Swarm, Mesos/Marathon, Kubernetes, Consul, Etcd, Zookeeper, BoltDB, Rest API, file...) to manage its configuration automatically and dynamically. On the other hand, Varnish is detailed as "High-performance HTTP accelerator". Varnish Cache is a web application accelerator also known as a caching HTTP reverse proxy. You install it in front of any server that speaks HTTP and configure it to cache the contents. Varnish Cache is really, really fast. It typically speeds up delivery with a factor of 300 - 1000x, depending on your architecture.
Traefik can be classified as a tool in the "Load Balancer / Reverse Proxy" category, while Varnish is grouped under "Web Cache".
"Kubernetes integration" is the top reason why over 10 developers like Traefik, while over 99 developers mention "High-performance" as the leading cause for choosing Varnish.
Traefik and Varnish are both open source tools. It seems that Traefik with 23K GitHub stars and 2.36K forks on GitHub has more adoption than Varnish with 908 GitHub stars and 216 GitHub forks.
According to the StackShare community, Varnish has a broader approval, being mentioned in 1003 company stacks & 135 developers stacks; compared to Traefik, which is listed in 46 company stacks and 17 developer stacks.