4 ms·

I'm glad to see Yahoo put this project out in the open source world. What I'm having a hard time with is understanding precisely where it fits after having rea

by jbyers 17y ago

I'm glad to see Yahoo put this project out in the open source world. What I'm having a hard time with is understanding precisely where it fits after having read through all the public docs. Despite the comparisons drawn on the intro page, Traffic Server seems close to squid and varnish functionally, but really only close to squid in actual implementation: a highly configurable split ram/disk caching proxy. Varnish is quite a departure from this approach (http://varnish.projects.linpro.no/wiki/ArchitectNotes http://varnish.projects.linpro.no/wiki/ArchitectNotes), and nginx at its core is not a caching proxy at all. This doesn't diminish its value as a system that's served tremendous traffic volumes over the last decade, but I'd love a more complete description of why I should choose TS over the alternatives in caching and reverse proxy roles.

blasdel 17y ago
Ha, I was just googling a range of years along with keywords trying to find that very article. Traffic Server looks to be well designed and implemented (especially compared to Squid), but it's still based on exactly the same idiotic 1975 assumptions.
chrisbolt 17y ago
nginx does caching reverse proxying now, as of 0.7.48 http://wiki.nginx.org/NginxHttpProxyModule#proxy_cache http://wiki.nginx.org/NginxHttpProxyModule#proxy_cache
- jbyers 17y ago
  It's been in for about five months and seems to be undergoing heavy development. Like everything else nginx I'm sure it will be rock solid, but I don't think it can be considered core yet.