Previously (not necessarily as solutions for this application stack) many have used alternatives including Memcached, MongoDB, CouchDB, Cassandra etc., and Redis was tested and compared to these other solutions - if only mentally. Ultimately while they are all good solutions …
UI isn't that great compared to the other competitors. The management of our memcached cluster was becoming pretty complicated as the application grew in size. Redis is a much better option compared to memcached. Redis is bit unreliable compared to the alternative RabbitMQ …
Vice President, Chief Architect, Development Manager and Software Engineer
Chose Redis™*
All are good products. MongoDB is a great NoSQL DB but didn't seem to have the high performance caching of Redis. Coherence and Xtreme Scale are expensive. In my opinion for our particular use case, Redis was the clear winner.
Redis is faster, provides documents JSON-wise with the proper odule and it is far more stable than MongoDB (we had really bad experiences with Mongo, especially when ops tends to increase).
DynamoDB is a fully managed key-value store by Amazon. It provides more powerful indexing to the tables, which certainly increases the performance if searching is what you need. However, it is also a lot more expensive to use compared to Redis. If your use case is more on the …
We evaluated Oracle and at first it seems competitive but after the contract term pricing would jump. Heard this from business associates and online communities
ElastiCache also offers Redis, but it's quite cryptic and you have to pay for support separately (it's quite expensive as well). With Redis Enterprise we were able to set-up our cluster with constant support from their team, and we were even able to set-up a particular set of …
We initially used Memcached for some of the caching and locking solutions we now use Redis for; we found that for the purposes of our system Memcache could not match up to Redis for performance. We also found Redis to be a bit more reliable, but that could have just been down …
Every time you don't need a document DB, you can't go wrong with Redis over MongoDB. Google Cloud Pub/Sub may have solved one use case, but we'd still have to deploy Redis instances for other use cases, and adding another tech stack would only add complexity to our …
We are big users of MySQL and PostgreSQL. We were looking at replacing our aging web page caching technology and found that we could do it in SQL, but there was a NoSQL movement happening at the time. We dabbled a bit in the NoSQL scene just to get an idea of what it was about …
We initially tried ElastiCache with Redis hosting. While it did the job of running Redis, we still had to deal with server sizing. We switched to Redis Cloud since that had auto-scaling and easy to use tools.