> > In my specific scenario, I am going to depend on Akamai for edge > > delivery and caching. I do not expect much hits to the infrastructure > > because Akamai will presumably cache all the static contents. So does > > it makes to have ATS cache static contents for Akamai to consume? > > My impression of Akamai was that, among other things, its role is > also to reduce load on your servers. > > > I expect to use Apache Httpd in my architecture to serve static > > contents, as well as proxy and mod_pagespeed, but I am not sure if > > ATS > > makes sense for me if I plan on using both Apache Httpd and Akamai. > > Do you expect Akamai to put such a load on your servers, that you > have a need to reduce this pain with ATS, if so, then by all means, > go for it. BUT: > > Please consider: You're introducing another layer into your system. > And hence the system's complexity. >
Hi Igor, I am under the same impression as well. For the purpose of content delivery, at this point I think I will rely on Akamai first, then introduce ATS if needed. I was wondering if people are using ATS in other situations, for example, the usage described here http://www.mnot.net/blog/2007/12/12/stale. Unfortunately, these features are not yet available in ATS (or Squid or Varnish) yet. Recently, I've been exploring ATS as a caching layer between our development environment and the web services we use. This would allow us to test against stateless web services during development without putting unnecessary strain against the origin servers.
