Apache Traffic Server
trafficserver.apache.org
Apache Traffic Server
1–10 of 40 posts
Re: Apache Traffic Server
#2Re: Apache Traffic Server
#3 - this tool (apache traffic server)
- regular apache can proxy/cache/route
- nginx
- traefik
- haproxy
- envoy
- kong
- ...more
Then it also somewhat intersects with less directly related things in other spaces, like squid, varnish, istio, and so on.Is there some document somewhere that goes over the choices, overlaps, etc?
Re: Apache Traffic Server
#4Looks recent, at first I thought it was webserver from the 90's...
Re: Apache Traffic Server
#5Looks recent, at first I thought it was webserver from the 90's...
Re: Apache Traffic Server
#6Lots of choices in the this space... - this tool (apache traffic server) - regular apache can proxy/cache/route - nginx - traefik - haproxy - envoy - kong - ...more Then it also somewhat intersects with less directly related things in other spaces, like squid, varnish, istio, and so on. 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].
Re: Apache Traffic Server
#7My impression from the comments is, that at least back then, it could be faster than things like Nginx or Varnish
Re: Apache Traffic Server
#8Lots of choices in the this space... - this tool (apache traffic server) - regular apache can proxy/cache/route - nginx - traefik - haproxy - envoy - kong - ...more Then it also somewhat intersects with less directly related things in other spaces, like squid, varnish, istio, and so on. Is there some document somewhere that goes over the choices, overlaps, etc?
> 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]. [1] http://…
Re: Apache Traffic Server
#9Looks recent, at first I thought it was webserver from the 90's...
Well, old ideas are indeed new once everyone forgets they were a thing. Nowadays CDNs and edge caches and web accelerators are seeing a resurgence, and in practice they can mean having an instance of Apache Traffic Server deployed somewhere.
Re: Apache Traffic Server
#10Looks like the "News" is that Nov 2 they released 8.1.3 and 9.1.1 with "security fixes". However, after digging for half an hour I can't tell what the nature of the security fix is. Changelogs and issues related to these releases don't highlight any particular security issues or what the impacts are.