Memcached or Redis? It’s a question that nearly always arises in any discussion about squeezing more performance out of a modern, database-driven web application. When performance needs to be improved, caching is often the first step taken, and Memcached or Redis are typically the first places to turn.These renowned cache engines share a number of similarities, but they also have important differences. Redis, the newer and more versatile of the two, is almost always the superior choice.
[ Which NoSQL database should you use? Let InfoWorld be your guide. NoSQL standouts: The best key-value databases. | NoSQL standouts: The best document databases. | Keep up with the hottest topics in programming with InfoWorld’s App Dev Report newsletter. ]
Redis vs. Memcached for caching
Let’s start with the similarities.
Both Memcached and Redis serve as in-memory, key-value data stores, although Redis is more accurately described as a data structure store.
Both Memcached and Redis belong to the NoSQL family of data management solutions, and both are based on a key-value data model.
They both keep all data in RAM, which of course makes them supremely useful as a caching layer.
In terms of performance, the two data stores are also remarkably similar, exhibiting almost identical characteristics (and metrics) with respect to throughput and latency.To read this article in full or to leave a comment, please click here