Just to clarify things since I helped write the initial blog post about twemcache... in our original post, we had an error regarding the slab calcification problem we mentioned, this problem ONLY applied to our v1.4.4 fork of memcached. After speaking with the upstream maintainers, we learned that recent memcached versions have addressed some of these problems. These are the type of conversations we want to have.<p>At the time we adopted memcached, that's the version we went with and made sure it worked well in our production environment as we scaled as a company. We also open sourced twemproxy [<a href="https://github.com/twitter/twemproxy" rel="nofollow">https://github.com/twitter/twemproxy</a>] which is a lightweight proxy for memcached which has worked well for us in combination with twemcache and may work well for others too.<p>We just want to reiterate that twemcache has worked well for our unique environment and any teams evaluating memcached should try all their try all their options, just like any other piece of software you adopt in your stack.<p>One of the reasons of open sourcing our work was to share our ideas with the memcached community to see what worked well for us and help everyone. For example, this is also how we treat our work with our MySQL fork [<a href="https://github.com/twitter/mysql" rel="nofollow">https://github.com/twitter/mysql</a>] which we maintain in the open and have signed an OCA with Oracle to help get work pushed upstream so everyone benefits in the long run.