Service Architecture - SOA: HTTP Cache and the need for cachability

, Oct 16, 2008

Good advice on HTTP app design from unexpected sources:

So HTTP Cache on its own doesn't make your application perform any better for end users or reduce the load on your servers. You have to design your application so the elements being returned are cachable in a way that will deliver performance improvements. For some applications its trivial, for others (like the Mandelbrot Map) its a little bit harder.

On October 16, 2008 11:12 PM, Bill de hÓra said:

And then there’s this:

http://service-architecture.blogspot.com/2008/05/rest-on-mars-scaling-problem-to-make.html

Steve seems smart enough, but pretending technology doesn’t matter in combination with making your business depend on services that aren’t inherently stable I doubt helps the bottom line (if the business itself isn’t stable and is in constant change how will business driven services not end up a mess?).

On October 19, 2008 2:12 PM, Stefan Tilkov Author Profile Page said:

I agree with your criticism of that particular (and many others) of Steve’s posts - as I said, unexpected source :-)