A few memcached-related blog posts over the last couple of days.

First, Tobias Luetke gives the the secret to memcached. It boils down to being as specific as you can with your memcached requests. In his example, part of the key was a version number which gets revved any time an update to a product is done. That way, cache misses will occur automatically after an update without trying to manage a full sweep of the cache.

Second, Greg Luck compares Ehcache with memcached and finds Ehcache to be faster. That’s somewhat understandable since Ehcache is being a local cache and obviously memcached has the network overhead for any put/get. I think these two have different roles and it isn’t that useful of a comparison. Kevin Burton has some additional thoughts on the benchmarks.

Technorati Tags:
memcached, ehcache

• BROWSE / IN TIMELINE
• « Ignite Where
• » Extending Philadelphia Wireless

• BROWSE / IN Development
• « Ignite Where
• » Creating a Web Framework with Conventions