Chapter 9. Redis Cluster and Redis Sentinel (Collective Intelligence)
Redis was initially designed to be very lightweight and fast. Previously, the only topology available for anyone using Redis was master/slave, in which the master receives all the writes and replicates the changes to the slave (or slaves). This happens without any sort of automatic failover or data sharding. This topology works well in many scenarios, such as when:
- The master has enough memory to store all of the data that you need
- More slaves can be added to scale reads better or when network bandwidth is a problem (the total read volume is higher than the hardware capability)
- It is acceptable to stop your application when maintenance is required on the master machine
- Data redundancy ...
Get Redis Essentials now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
