> Is there some document somewhere that goes over the choices, overlaps, etc?
I believe Apache Traffic Server doesn't really compete with the likes of nginx or traefik. Apache Traffic Server is a HTTP caching server/web accelerator, thus it's specialized for caching HTTP requests and consequently it's simpler to deploy and configure. With that in mind, it competes with the likes of Squid[1] or Varnish[2].
It does support routing via SNI. And of course, people do use nginx (and other tools) just as proxy caches. That's sort of what I was getting at, lots of overlap and sub-niches.
I've used varnish in the past with cdn's, never had an issue so I have not tried other cashing/load balancing products.
Internally use squid with rules for non routed internal network addresses.
Sounds like lots of newer products out there, maybe even better products, but you sometimes just stay with whats working due to time/budgets.
Would really be interested in articles with benchmarks, pros/cons, etc on different products. Wonder why not many websites doing this for content? Sounds like a good market that needs filled.
I believe Apache Traffic Server doesn't really compete with the likes of nginx or traefik. Apache Traffic Server is a HTTP caching server/web accelerator, thus it's specialized for caching HTTP requests and consequently it's simpler to deploy and configure. With that in mind, it competes with the likes of Squid[1] or Varnish[2].
[1] http://www.squid-cache.org/
[2] https://varnish-cache.org/