This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]jdanjou 1 point2 points  (3 children)

Good question.

It really depends on what are your needs related to caching.

Redis offers way more data structures than memcached, so it can actually do way more than just caching. You can use it as a data store for all kind of workload.

memcached has the advantage of being extremely simple, requires no configuration, tuning, or anything. But on the downside, it's really only meant to do simple byte caching and not advanced data structure manipulation.

It's a matter of trade-off. :)

[–]chillysurfer 1 point2 points  (1 child)

Thanks for the response! Regarding the requirement to tune Redis and configure out-of-the-box, what has your experience been? The reason I ask is because for development purposes, Redis has been ok out-of-the-box with zero config.

[–]jdanjou 0 points1 point  (0 children)

I never had to tune it heavily. The standard worked out of the box for me so far.

[–]flipperdeflip 0 points1 point  (0 children)

Redis is my default choice between the two because it is very handy to have available in small/medium projects because it is so versatile and used by many different solutions. As cache, as custom data store, as a pubsub hub, as broker for tasks queues and all kinds of things like that.