Specifically, I install it, point it at a large raw disk partition, and drop in my config files (largely consisting of routing rules for where to get the origin based on the request), and trafficserver just goes to town. It's a perfect use case for the ephemeral storage on virtual instances.
Those who had to deal with nginx plugins, I feel your pain...
why wouldn't Lua be a solution here?
openresty is (patched) nginx + luajit
haproxy has optional extension with lua as well
CMIIAW, what parent is saying is he does not like lua for this purpose
one of the nice things about haproxy is that pcre is optional. it seems pcre is a hard requirement to compile trafficserver
trafficserver is also much more code, coming from a variety of sources.
- this tool (apache traffic server)
- regular apache can proxy/cache/route
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 or Varnish.
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.
Some companies that use it at very large scale don't like to talk about what technologies they use.
Been to many ATS meetups, even worked on atscppapi years ago. Very robust plugin capabilities.
(Vercel uses nginx)
My impression from the comments is, that at least back then, it could be faster than things like Nginx or Varnish
Looks 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.
I submitted the link before the new release with security fixes was announced, without that in mind. Moreover, the link points to the project page and not the release. I submitted because I found the project interesting but somewhat low-key, and I thought people like me would find it interesting.
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.