http://simonwillison.net/2009-02-23T08:28:00+00:00Simon Willison2009-02-23T08:28:00+00:002009-02-23T08:28:00+00:00https://simonwillison.net/2009/Feb/23/building/#atom-tag

<p><strong><a href="http://axonflux.com/building-and-scaling-a-startup">Building and Scaling a Startup on Rails: 12 Things We Learned the Hard Way</a></strong></p> Lessons learned from Posterous. Some good advice in here, in particular “Memcache later: If you memcache first, you will never feel the pain and never learn how bad your database indexes and Rails queries are”. Also recommends using job queues for offline processing of anything that takes more than 200ms. <p>Tags: <a href="https://simonwillison.net/tags/memcache">memcache</a>, <a href="https://simonwillison.net/tags/message-queues">message-queues</a>, <a href="https://simonwillison.net/tags/posterous">posterous</a>, <a href="https://simonwillison.net/tags/rails">rails</a>, <a href="https://simonwillison.net/tags/scaling">scaling</a></p>

2009-01-27T20:27:41+00:002009-01-27T20:27:41+00:00https://simonwillison.net/2009/Jan/27/sharding/#atom-tag

<p><strong><a href="http://code.google.com/appengine/articles/sharding_counters.html">Sharding Counters on Google App Engine</a></strong></p> “While the datastore for App Engine scales to support a huge number of entities it is important to note that you can only expect to update any single entity, or entity-group, about five times a second”. This article explains a technique for sharding writes across multiple counters in detail, including a way to keep a memcache counter updated at the same time for faster reads. <p>Tags: <a href="https://simonwillison.net/tags/caching">caching</a>, <a href="https://simonwillison.net/tags/google">google</a>, <a href="https://simonwillison.net/tags/google-app-engine">google-app-engine</a>, <a href="https://simonwillison.net/tags/memcache">memcache</a>, <a href="https://simonwillison.net/tags/python">python</a>, <a href="https://simonwillison.net/tags/scaling">scaling</a>, <a href="https://simonwillison.net/tags/sharding">sharding</a></p>

2009-01-05T12:37:15+00:002009-01-05T12:37:15+00:00https://simonwillison.net/2009/Jan/5/memcachedb/#atom-tag

<p><strong><a href="http://memcachedb.org/">MemcacheDB</a></strong></p> A server that speaks the memcache protocol but uses Berkeley DB for reliable persistent storage. Speedy: 20,000 writes/second and 60,000+ reads/second. Includes a full replication mechanism (with custom memcache protocol commands) based on Berkeley DB’s. <p>Tags: <a href="https://simonwillison.net/tags/berkeleydb">berkeleydb</a>, <a href="https://simonwillison.net/tags/keyvaluepairs">keyvaluepairs</a>, <a href="https://simonwillison.net/tags/memcache">memcache</a>, <a href="https://simonwillison.net/tags/memcachedb">memcachedb</a>, <a href="https://simonwillison.net/tags/replication">replication</a>, <a href="https://simonwillison.net/tags/scaling">scaling</a></p>

2008-05-28T23:11:06+00:002008-05-28T23:11:06+00:00https://simonwillison.net/2008/May/28/memcache/#atom-tag

<p><strong><a href="http://code.google.com/appengine/docs/memcache/usingmemcache.html">Using Memcache with Google App Engine</a></strong></p> Brad Fitzpatrick’s 20% time project. <p>Tags: <a href="https://simonwillison.net/tags/brad-fitzpatrick">brad-fitzpatrick</a>, <a href="https://simonwillison.net/tags/google">google</a>, <a href="https://simonwillison.net/tags/google-app-engine">google-app-engine</a>, <a href="https://simonwillison.net/tags/memcache">memcache</a></p>

2007-12-15T01:59:23+00:002007-12-15T01:59:23+00:00https://simonwillison.net/2007/Dec/15/nginxmemcachedmodule/#atom-tag

<p><strong><a href="http://wiki.codemongers.com/NginxMemcachedModule">NginxMemcachedModule</a></strong></p> nginx can be set up to directly serve a URL from memcache if the corresponding cache key is set, and fall back to a backend application server otherwise. Application servers can then write directly to memcache when content needs to be cached or goes stale. <p>Tags: <a href="https://simonwillison.net/tags/caching">caching</a>, <a href="https://simonwillison.net/tags/memcache">memcache</a>, <a href="https://simonwillison.net/tags/memcached">memcached</a>, <a href="https://simonwillison.net/tags/nginx">nginx</a>, <a href="https://simonwillison.net/tags/scaling">scaling</a></p>

2007-07-05T00:56:33+00:002007-07-05T00:56:33+00:00https://simonwillison.net/2007/Jul/5/caching/#atom-tag

<p><strong><a href="http://www.koziarski.net/archives/2007/5/28/clever-caching">Clever Caching</a></strong></p> Instead of invalidating your cache directly, bump a version number on your model (blog entry or whatever) and use that as part of the cache key. This also gives you dynamic etags for free. <p>Tags: <a href="https://simonwillison.net/tags/caching">caching</a>, <a href="https://simonwillison.net/tags/etags">etags</a>, <a href="https://simonwillison.net/tags/memcache">memcache</a>, <a href="https://simonwillison.net/tags/michael-koziarski">michael-koziarski</a></p>

2007-04-20T06:50:51+00:002007-04-20T06:50:51+00:00https://simonwillison.net/2007/Apr/20/libketama/#atom-tag

<p><strong><a href="http://www.last.fm/user/RJ/journal/2007/04/10/392555/">libketama</a></strong></p> A consistent hashing algorithm for memcache clients, from the team at last.fm. <p><small></small>Via <a href="http://del.icio.us/deusx">Les Orchard</a></small></p> <p>Tags: <a href="https://simonwillison.net/tags/hashing">hashing</a>, <a href="https://simonwillison.net/tags/lastfm">lastfm</a>, <a href="https://simonwillison.net/tags/les-orchard">les-orchard</a>, <a href="https://simonwillison.net/tags/memcache">memcache</a></p>