We have Spring Boot 2 application that uses Redis as the cache manager. We deploy our application on Amazon AWS where we use AWS ElastiCache Redis service in cluster mode disabled. Our setup includes a Redis master with two Redis slaves. The default Java client for Redis with
spring-boot-starter-data-redis dependency is
lettuce-core. When you are working with single Redis node with no slaves, using AWS Elastic Cache Redis is as simple as providing the
spring.redis.url with the value of AWS ElastiCache Redis instance URL. This was the set up that we were using till a month back. As the load on the system increased we decided to use ElastiCache Redis in replicated setup to scale our reads. In AWS, Redis implements replication in two ways:
- With a single shard that contains all of the cluster’s data in each node – Redis (cluster mode disabled)
- With data partitioned across up to 15 shards — Redis (cluster mode enabled)
In our case, cached data is less than 1 GB so it fits in RAM of single node. This made us choose cluster mode disabled setup.