Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Apache Traffic Server

trafficserver.apache.org

Post reply on HN
Print view View original

21–30 of 40 posts

Re: Apache Traffic Server

#21

Post by VWWHFSfQ »

dig1 wrote: post #11

Although haproxy and nginx cover (for me) almost all use-cases I had to deal with (with OpenResty [1] as a backup), I see one place where ATS could shine: plugins. From examples [2], C API looks sane and well documented, and this is very important if you want to add some custom stuff inside your proxy server without losing your hair. And no, lua isn't the solution here ;) Those who had to deal with nginx plugins, I f…

> And no, lua isn't the solution here

why wouldn't Lua be a solution here?

Re: Apache Traffic Server

#22

Post by cduzz »

cstivers1978 wrote: post #19
Thaxll wrote: post #2

Looks recent, at first I thought it was webserver from the 90's...

This was originally “Yahoo! Traffic Server”, was developed by Yahoo! in the early 2000’s and was used in part to power Yahoo! CDN. At the time Yahoo! relied on Akamai and its own network.

It was developed by inktomi[1]; inktomi was acquired by yahoo in the one of the great extinction events of the early internet.

[1]https://en.wikipedia.org/wiki/Inktomi

Re: Apache Traffic Server

#23

Post by sciurus »

tyingq wrote: post #3

Lots 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?

Why do you describe it as less directly related to squid and varnish? I haven't worked with ATS before, but it's documentation describes it as "a high-performance web proxy cache that improves network efficiency and performance by caching frequently-accessed information at the edge of the network" which makes it seem to fill a similar role as them.

Re: Apache Traffic Server

#24

Post by tyingq »

sciurus wrote: post #23
tyingq wrote: post #3

Lots 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?

Why do you describe it as less directly related to squid and varnish? I haven't worked with ATS before, but it's documentation describes it as "a high-performance web proxy cache that improves network efficiency and performance by caching frequently-accessed information at the edge of the network" which makes it seem to fill a similar role as them.

Yes, you're right, though that sort of goes to my question :)

Re: Apache Traffic Server

#25

Post by CameronNemo »

tyingq wrote: post #3

Lots 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?

Istio is primarily just a wrapper around Envoy, no?

Re: Apache Traffic Server

#26

Post by lumanaughty14 »

Almost everyone is an end user of Apache Traffic Server without really knowing it. It is used by Yahoo, Apple, Comcast, Wikipedia, AT&T, Cox and many other companies.

Some companies that use it at very large scale don't like to talk about what technologies they use.

Re: Apache Traffic Server

#27

Post by IronWolve »

nuerow wrote: post #6
tyingq wrote: post #3

Lots 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://…

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.

Re: Apache Traffic Server

#28

Post by thatwasunusual »

tyingq wrote: post #3

Lots 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?

Varnish?

Re: Apache Traffic Server

#30

Post by otterley »

VWWHFSfQ wrote: post #21
dig1 wrote: post #11

Although haproxy and nginx cover (for me) almost all use-cases I had to deal with (with OpenResty [1] as a backup), I see one place where ATS could shine: plugins. From examples [2], C API looks sane and well documented, and this is very important if you want to add some custom stuff inside your proxy server without losing your hair. And no, lua isn't the solution here ;) Those who had to deal with nginx plugins, I f…

> And no, lua isn't the solution here why wouldn't Lua be a solution here?

Too slow for a proxy cache of ATS's caliber/audience.
Post reply on HN