Home Database Redis The difference between redis cluster and distributed

The difference between redis cluster and distributed

Nov 22, 2019 pm 02:24 PM
redis

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!

Statement of this Website
The content of this article is voluntarily contributed by netizens, and the copyright belongs to the original author. This site does not assume corresponding legal responsibility. If you find any content suspected of plagiarism or infringement, please contact admin@php.cn

Hot AI Tools

Undresser.AI Undress

Undresser.AI Undress

AI-powered app for creating realistic nude photos

AI Clothes Remover

AI Clothes Remover

Online AI tool for removing clothes from photos.

Undress AI Tool

Undress AI Tool

Undress images for free

Clothoff.io

Clothoff.io

AI clothes remover

Video Face Swap

Video Face Swap

Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Tools

Notepad++7.3.1

Notepad++7.3.1

Easy-to-use and free code editor

SublimeText3 Chinese version

SublimeText3 Chinese version

Chinese version, very easy to use

Zend Studio 13.0.1

Zend Studio 13.0.1

Powerful PHP integrated development environment

Dreamweaver CS6

Dreamweaver CS6

Visual web development tools

SublimeText3 Mac version

SublimeText3 Mac version

God-level code editing software (SublimeText3)

How to build the redis cluster mode How to build the redis cluster mode Apr 10, 2025 pm 10:15 PM

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 read redis queue How to read redis queue Apr 10, 2025 pm 10:12 PM

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.

How to clear redis data How to clear redis data Apr 10, 2025 pm 10:06 PM

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.

How to configure Lua script execution time in centos redis How to configure Lua script execution time in centos redis Apr 14, 2025 pm 02:12 PM

On CentOS systems, you can limit the execution time of Lua scripts by modifying Redis configuration files or using Redis commands to prevent malicious scripts from consuming too much resources. Method 1: Modify the Redis configuration file and locate the Redis configuration file: The Redis configuration file is usually located in /etc/redis/redis.conf. Edit configuration file: Open the configuration file using a text editor (such as vi or nano): sudovi/etc/redis/redis.conf Set the Lua script execution time limit: Add or modify the following lines in the configuration file to set the maximum execution time of the Lua script (unit: milliseconds)

How to use the redis command line How to use the redis command line Apr 10, 2025 pm 10:18 PM

Use the Redis command line tool (redis-cli) to manage and operate Redis through the following steps: Connect to the server, specify the address and port. Send commands to the server using the command name and parameters. Use the HELP command to view help information for a specific command. Use the QUIT command to exit the command line tool.

How to set the redis expiration policy How to set the redis expiration policy Apr 10, 2025 pm 10:03 PM

There are two types of Redis data expiration strategies: periodic deletion: periodic scan to delete the expired key, which can be set through expired-time-cap-remove-count and expired-time-cap-remove-delay parameters. Lazy Deletion: Check for deletion expired keys only when keys are read or written. They can be set through lazyfree-lazy-eviction, lazyfree-lazy-expire, lazyfree-lazy-user-del parameters.

How to optimize the performance of debian readdir How to optimize the performance of debian readdir Apr 13, 2025 am 08:48 AM

In Debian systems, readdir system calls are used to read directory contents. If its performance is not good, try the following optimization strategy: Simplify the number of directory files: Split large directories into multiple small directories as much as possible, reducing the number of items processed per readdir call. Enable directory content caching: build a cache mechanism, update the cache regularly or when directory content changes, and reduce frequent calls to readdir. Memory caches (such as Memcached or Redis) or local caches (such as files or databases) can be considered. Adopt efficient data structure: If you implement directory traversal by yourself, select more efficient data structures (such as hash tables instead of linear search) to store and access directory information

How to implement redis counter How to implement redis counter Apr 10, 2025 pm 10:21 PM

Redis counter is a mechanism that uses Redis key-value pair storage to implement counting operations, including the following steps: creating counter keys, increasing counts, decreasing counts, resetting counts, and obtaining counts. The advantages of Redis counters include fast speed, high concurrency, durability and simplicity and ease of use. It can be used in scenarios such as user access counting, real-time metric tracking, game scores and rankings, and order processing counting.

See all articles