AS A sysadmin
I WANT to be able to restart the memcached instances without breaking the user experience
SO THAT I don't have to co-ordinate with the user base to perform basic sysadmin

GIVEN a service that uses memcached
WHEN memcached entirely disappears
THEN other services should still function (but perhaps be slower)

GIVEN a service that uses memcached
WHEN memcached data is lost (e.g. due to a restart, or cache full)
THEN other services should still function (but perhaps be slower)

It should be possible to lose memcached at any time, and the effect to the user should be negligible. I believe the release editor violates this principal, by storing session data in memcached.