Posted by matt in Architecture, Performance
on Oct 12th, 2009 | 2 comments
Before you read on this isn’t a post devoted to image caching. This is a post about data caching in general with image caching being an extreme form of data caching. It comes from a bit of work I did recently caching data from a tracking feed. It’s based around why you want to cache, what data you might need to cache and how you might cache (I used .NET but you can do it in all major web development languages). Caching has often been the premise of web sites that want to be, and I’m using a technical terms here, ‘screamingly fast’ and not ‘snail slow’.
Caching before caching was...