On 3/13/12 3:06 PM, Van Doorn, Jan R wrote:
I'm a little bit worried about the clustering feature, as I think I want to be able to have different types of caches in a single location, and this is an ATS "proprietary" feature implementation, correct?
Correct.
But yes - that is really what I want - a distributed cache within the colo where each object is on one single cache.
I don't see how ICP would solve it either. First of all, it generally doesn't implement "hashing", i.e. any and all objects can keep a copy of an object. What's worse, it only uses the URL, and nothing from the header, when selecting which alternate to serve.
Parent proxying is different, but that sort of turns your proxy into a L7 load balancer. You can still cache things locally (perhaps with a small SSD + large RAM that can deal with significant cache churning), but now you're turning it into a router basically. Nothing wrong with that at all of course. I would do the same, heck, I did the same :).
You can probably write something using that parent API I mentioned. There's also a partial plugin to implement L7 load balancing in the plugin Git repository. It unfortunately is not functional, since several key pieces were not possible for Yahoo to Open Source.
Cheers, -- Leif
