Memcached on top of Redis?
I read a couple of posts[1] talking about Gear6 Memcached native query support and Redis integration. Anyways, based on the details I’ve found so far[2], what I understand is:
- Gear6 memcached provides an enhanced API that allows querying the key/value space
- Gear6 memcached is looking to support more data types by using Redis support for types like lists, sets, ordered sets, hashes[3]
- or Gear6 is looking to provide commercial support for Redis
These left me with the question: why would you use memcached on top of Redis?
Possible answers:
- if the integration would preserve the same memcached API (nb I am not sure though this would be possible) then
- such a product might be useful for projects needing both RDBMS and Redis (note: but in the end the project would still need to be aware of both storage APIs)
such a product might be useful for transitioning towards Redis alone
the integration would just add features missing from the current version of Redis (f.e. elastic scaling, sharding, etc.)
Do you see any other reasons for using memcahed on top of Redis?
References
-
[1] Posts:
- ☞ NoSQL player questions big data (nb the title has pretty much nothing to do with the article)
- ☞ Gear6 Enhances Memcached to Include Native Query Support and Redis Integration
-
[2] The only documentation I’ve found about cache query is ☞ here and the only mention to Redis integration found ☞ here talks only about support for Redis: (↩)
Gear6 currently offers commercial support for Memcached. If you are interested in purchasing support for Redis please contact us.
Gear6 will soon contribute a number of enhancements to the Redis community.
- [3] You can read more about Redis data types ☞ here (↩)