Gets the job done before you know which job that is

Pros

It makes clustering, sharding, backups and more very easy to setup, control and monitor

Cons

The prices are a bit too high for small projects, it's ok for an enterprise global solution

Implementation was simple, we setup a multi-site active-active cluster in 30 minutes!

Our experience was great, we were able to accomplish our goals and the support team was more than generous with there time.

Pros

Redis Enterprise provide the ability to make our application highly available using their XDCR feature. We setup a multi-data center cluster the replicated in real-time so that we could design our application to actively server from multiple data centers without any additional latency.

Cons

It needs a better UI, I would definitely like to be able to exec commands without having to login to the hosts.

Redis Enterprise - OSS or Enterprise

Overall, I would really appreciate the Redis Enterprise engagement especially the support as that is something (apart from cluster support) which really makes it shine.

Pros

The pros over other solutions and its open source versions include: 1) On the fly scaling Scale to more/less cores and memory as and when needed. 2) Cluster support Support for clusters unlike the OSS version where the cap is on 1 core and fixed memory. 3) High availability & automatic failover Redis enterprise manages the failover internally, so no crashes. 4) Predefined SLAs A mandatory spec definition required by most enterprise customers 5) Monitoring, alerts, etc all such services are available Get notifications on configurable events

Cons

Well, the pricing may not be very well suited for small companies which are low on budget. Not really a con as the open source version does most of the things except for the cluster support on the technical side of things.

The best solution to use as cache

I use Redis on a daily basis to reduce the load on database servers and increase application performance. All calls to my APIs first make queries on Redis and only in case of error go to the database, this ensures greater speed in the responses. However, good planning is necessary to ensure synchronization between the SQL database and REDIS. In addition to a good maturity to map data from one database to another.

Pros

I liked the simplicity of creating and retrieving keys and the integrations available with different programming languages

Cons

The documentation is a bit complex for those who have never had contact with the product, understanding some concepts of how to use the key types takes a while.

Many integrations Database

Experimental applications / demos for prospective apps / labs, Open Source mostly.

Pros

If I, as a developer, had the luxury of choosing a database by just a logo or colour palette initially, I would definitely choose a Redis (Redis Enterprise) because one of my favourite colours is scarlet. Surely there are other reasons for liking Redis: intuitiveness, innovative features, flexibility, scalability, ecosystem.

Cons

Since I use Redis Enterprise only in experimental applications / demos for prospective apps / labs, no issues so far.