A coworker and I were having a discussion about whether to use MySQL or memcached for a key-value store. My view is that memcached is designed to be exactly that, and if we desire persistence we can use Membase. He alleged that memcached lacks read/write consistency, such that you can end up reading a half-value if you were to read in the middle of a write. Is this true? I have used memcached under many thousands of reads/writes per second on a high traffic site and never ran into any such problem.
-- --- You received this message because you are subscribed to the Google Groups "memcached" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
