title: Couchbase memcached bucket alternatives
body: <p>I'm currently looking for a solution for a distributed cache provider. At the moment I'm thinking of Couchbase 3 server, using Memcached bucket. I am not sure though, that it's the right thing I need. I don't need disk persistence and replication, because the information is not crucial, so Couchbase bucket does not seem so appropriate in this case. </p>
  
  <p>During my tests I experienced some problems with the memcached buckets - the .NET client does not react to node failure, allowing insertion of entries with already existing key(on the failed node). After the failed node comes back again, two documents exist with the same key, and only the first one is accessible. Also, I need to reinitialize the bucket object so it can be aware of the failovered node, or it keeps throwing 'ClientFailure' statuses on Get requests (and that's kind of slow operation). That and the 1 mb size limit per document makes me rethink if I'm on the right direction.</p>
  
  <p>Is there a better way to notify the client for failed nodes? And if not, can you recommend me another technology, suitable for my case?</p>