Memcache : because your database will

thank youhttp://netuality.ro

Spot theresemblance

Memcache stays "between" app serversand db - dumb/fast server,client "as smart as needed"

image © blogs.sun.com

Plan for success = no panic

image © www.jangro.com

3 implementations:

- "original" 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)

Memcached vs Tugela

- "normal" conditions, enough memory- negligible overhead

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

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 rocksmemcache.hash_strategy = consistent