Interesting behind-the-scenes look at how Twitter uses Redis: 10K+ instances, 100TB+ of memory, and ~40M QPS! All of the timelines are stored in Redis.. and that's a lot of memory!

The talk also covers the use of twemproxy aka nutcracker is a fast and lightweight proxy for memcached and redis protocol. It was primarily built to reduce the connection count on the backend caching servers.


https://github.com/twitter/twemproxy