varnish-towncrier VS traefik-kop

Having said that, varnish is an excellent tool for these situations and it also works well if you decide to use a CDN later on. We use the combination of varnish (caching for dynamic content) and Cloudflare (caching for static assets) in a couple of production environments and using the relatively recent CDN-Cache-Control headers it's finally pretty easy to separate cache control headers of various different links in your proxy chain. Be aware that cache tagging requires an additional module (xkey vmod) which isn't always shipped with varnish packages. To help with cache invalidations you can also use tools like Varnish Broadcaster (commercial) or (shameless plug) varnish-towncrier which decouples cache invalidation calls from varnish and doesn't require your application to directly talk to each varnish instance.

Traefik gives you a lot of options to accomplish this, you can use docker swarm, move to kubernetes or use any of their discovery providers. These options were rather complicated solutions for what I needed, so I decided to look around for other alternatives. Here I found Traefik-Kop, but it I still had to do a lot of manual work and open a different port for each container I wanted to be accesible through my reverse proxy.

The obvious solution is docker swarm/kubernetes, but if you don't want to go all the way there yet I can really recommend traefik kop. Very simple to setup, you just add a redis service next to the traefik instance and set it up as a provider, then you run traefik kop on every other machine, pointed at that redis service. Traefik kop will discover docker services on the machine and write everything to redis and it'll get picked up ny traefik. Worked like a charm!

Maybe this can help you https://github.com/jittering/traefik-kop