Taking expirations out of caching

Posted by David May 22, 2007 @ 04:07 PM

It’s been said that the two last hard problems in programming are naming things and expiring caches. The first is going to be hard to sidestep entirely, but what if we could the second? Tobi arrived at a eureka moment for just that using Memcached and various kinds of caching. Instead of manually expiring things, just ask for a specific version, and let the caching engine take care of dumping that which isn’t used any more.

Read more on The Secret to Memcached.

Posted in Tricks | 3 comments

Comments

Leave a response

  1. Peter Michaux on 22 May 16:31:

    That sounds a lot like using a time stamp on JavaScript and CSS files with far-future expiration dates. When a page loads, the browser checks it’s own cache for the specified version. If the browser doesn’t have the version then it asks the server.

  2. Slaweg on 26 May 13:48:

    Great and excellent article t’s realy helpful.

  3. E臣工作室官方博客 on 13 Jun 08:06:

    博客营销

Ruby on Rails was created by David Heinemeier Hansson, a partner at 37signals,
then extended and improved by a core team of committers and hundreds of open-source contributors.

Rails is released under the MIT license. Ruby under the Ruby License.

"Rails", "Ruby on Rails", and the Rails logo are trademarks of David Heinemeier Hansson. All rights reserved.

Sponsored by

 37signals