All 7 Redis vs Memcached questions
More in Redis vs Memcached
What are the fundamental differences between Redis and Memcached as caching solutions? How do the threading models of Redis and Memcached differ, and what performance implications does this have? What features does Redis offer that have no direct equivalent in Memcached, and how might these influence a technology choice? If a team is already using Memcached and considering a migration to Redis, what migration considerations and challenges should they plan for? How would you decide between Redis and Memcached for a large scale application with a purely simple, high volume string caching requirement and no need for advanced features? How does memory efficiency compare between Redis and Memcached for storing large numbers of small key value pairs?
Advertisement
Back to results for “Persistence (RDB/AOF)”
Redis › Redis vs Memcached

Does Memcached support data persistence the way Redis does with RDB and AOF?

Beginner

Answer

No, Memcached is purely an in memory cache with no built-in persistence mechanism, meaning all data is permanently lost if the Memcached process restarts or the server reboots, unlike Redis which can optionally persist data to disk, making Redis a better fit when you need your cached data to survive a restart.
-- Memcached data is entirely lost on restart
-- Redis can optionally survive a restart with RDB or AOF
Real-world example A team using Memcached purely for ephemeral, easily regenerated cached data is comfortable with the total data loss on restart, while a different team storing important session data specifically chooses Redis for its persistence capabilities.

Common follow-ups: What kinds of data are appropriate to store in a cache with no persistence at all?;How quickly can a completely empty cache be repopulated after a restart?

Persistence (RDB/AOF);Caching Patterns
All 7 Redis vs Memcached questions