1. Memcache : because
your database will
thank you
http://netuality.ro

3. Spot the
resemblance

4. Memcache stays quot;betweenquot; app servers
and db - dumb/fast server,
client quot;as smart as neededquot;
image © blogs.sun.com

5. Plan for success = no panic
image © www.jangro.com

6. 3 implementations:
- quot;originalquot; memcached
by Danga
danga.com/memcached/
- tugela memcache
(bdb, Wikipedia)
http://tinyurl.com/26jx5e
- memcachedb (bdb,
replicated, student
project on Google Code,
unstable)
- lots of contributions
(Facebook, LastFM)

7. Memcached vs Tugela
- quot;normalquot; conditions, enough memory
- negligible overhead

8. Memcached vs Tugela
- on a memory-constrained server
- 100/1000 simultaneous threads (stackless Python)
- ... and yet Tugela massively kicks ass

9. Tugela gotchas
- “no expiry policy management” = NO PURGING,
ITEMS DO EXPIRE
- but project not maintained any more. Forks
welcomed by the author (Domas Mituzas).
PHP programmer ?
- use UDP and consistent hashing implementation
from PECL, truly rocks
memcache.hash_strategy = consistent