The difference between redis cluster and distributed
Distribution refers to splitting the business system, that is, each distributed node implements different functions.
A cluster is a group of service entities that work together to provide a service platform that is more scalable and available than a single service entity. (Recommended learning: Redis Video Tutorial)
Simply put, distribution improves efficiency by shortening the execution time of a single task, while clustering improves efficiency by shortening the execution time of a single task. The number of tasks executed per unit time to improve efficiency.
Redis Cluster cluster mode usually has the characteristics of high availability, scalability, distribution, fault tolerance and other characteristics. There are generally two Redis distributed solutions:
Client partition scheme
The client has already decided which redis node the data will be stored in or read from. Get data. The main idea is to use a hash algorithm to hash the key of Redis data. Through the hash function, a specific key will be mapped to a specific Redis node.
The representative of the client partitioning scheme is Redis Sharding. Redis Sharding is a Redis multi-instance cluster method commonly used in the industry before Redis Cluster came out. Java's Redis client driver library Jedis supports the Redis Sharding function, namely ShardedJedis and ShardedJedisPool combined with the cache pool.
Advantages
No third-party middleware is used, the partitioning logic is controllable, the configuration is simple, there is no correlation between nodes, easy linear expansion, and strong flexibility.
Disadvantages
The client cannot dynamically add or delete service nodes. The client needs to maintain the distribution logic by itself. There is no connection sharing between clients, which will cause waste of connections.
Proxy partitioning scheme
The client sends a request to a proxy component, the proxy parses the client's data, forwards the request to the correct node, and finally replies the result to client.
Advantages: Simplified client distributed logic, transparent client access, low switching costs, and separation of proxy forwarding and storage. Disadvantages: There is an additional proxy layer, which increases the complexity of architecture deployment and performance loss.
The mainstream implementation solutions for proxy partitioning include Twemproxy and Codis.
Twemproxy
Twemproxy, also called nutcraker, is an open source intermediate proxy server program for redis and memcache by twitter. As a proxy, Twemproxy can accept access from multiple programs, forward it to various Redis servers in the background according to routing rules, and then return to the original route. Twemproxy has a single point of failure problem and needs to be combined with Lvs and Keepalived to create a high-availability solution.
Advantages: wide application range, high stability, and high availability of the intermediate proxy layer. Disadvantages: Inability to smoothly expand/shrink horizontally, no visual management interface, unfriendly operation and maintenance, failure to automatically transfer.
Codis
Codis is a distributed Redis solution. For upper-layer applications, there is no difference between connecting to Codis-Proxy and directly connecting to the native Redis-Server. The bottom layer of Codis will handle the forwarding of requests and perform data migration and other tasks without downtime. Codis uses a stateless proxy layer, and everything is transparent to the client.
Advantages
Implements high availability, data sharding and automatic balancing of the upper Proxy and underlying Redis, provides command line interface and RESTful API, and provides monitoring and management interfaces , Redis nodes can be added and deleted dynamically.
Disadvantages
The deployment architecture and configuration are complicated, it does not support cross-machine rooms and multi-tenants, and it does not support authentication management.
For more Redis-related technical articles, please visit the Introduction to Using Redis Database Tutorial column to learn!
The above is the detailed content of The difference between redis cluster and distributed. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

AI Hentai Generator
Generate AI Hentai for free.

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics



Redis cluster mode deploys Redis instances to multiple servers through sharding, improving scalability and availability. The construction steps are as follows: Create odd Redis instances with different ports; Create 3 sentinel instances, monitor Redis instances and failover; configure sentinel configuration files, add monitoring Redis instance information and failover settings; configure Redis instance configuration files, enable cluster mode and specify the cluster information file path; create nodes.conf file, containing information of each Redis instance; start the cluster, execute the create command to create a cluster and specify the number of replicas; log in to the cluster to execute the CLUSTER INFO command to verify the cluster status; make

How to clear Redis data: Use the FLUSHALL command to clear all key values. Use the FLUSHDB command to clear the key value of the currently selected database. Use SELECT to switch databases, and then use FLUSHDB to clear multiple databases. Use the DEL command to delete a specific key. Use the redis-cli tool to clear the data.

Using the Redis directive requires the following steps: Open the Redis client. Enter the command (verb key value). Provides the required parameters (varies from instruction to instruction). Press Enter to execute the command. Redis returns a response indicating the result of the operation (usually OK or -ERR).

Using Redis to lock operations requires obtaining the lock through the SETNX command, and then using the EXPIRE command to set the expiration time. The specific steps are: (1) Use the SETNX command to try to set a key-value pair; (2) Use the EXPIRE command to set the expiration time for the lock; (3) Use the DEL command to delete the lock when the lock is no longer needed.

To read a queue from Redis, you need to get the queue name, read the elements using the LPOP command, and process the empty queue. The specific steps are as follows: Get the queue name: name it with the prefix of "queue:" such as "queue:my-queue". Use the LPOP command: Eject the element from the head of the queue and return its value, such as LPOP queue:my-queue. Processing empty queues: If the queue is empty, LPOP returns nil, and you can check whether the queue exists before reading the element.

Redis uses a single threaded architecture to provide high performance, simplicity, and consistency. It utilizes I/O multiplexing, event loops, non-blocking I/O, and shared memory to improve concurrency, but with limitations of concurrency limitations, single point of failure, and unsuitable for write-intensive workloads.

The best way to understand Redis source code is to go step by step: get familiar with the basics of Redis. Select a specific module or function as the starting point. Start with the entry point of the module or function and view the code line by line. View the code through the function call chain. Be familiar with the underlying data structures used by Redis. Identify the algorithm used by Redis.

Redis, as a message middleware, supports production-consumption models, can persist messages and ensure reliable delivery. Using Redis as the message middleware enables low latency, reliable and scalable messaging.
