Adaptive Scenarios for Redis

Redis Application Scenario:

1. High concurrency for data read and write

2. Efficient storage and access to massive amounts of data

3. High scalability and high availability of data

Doing a distributed extension is simple, because there is no fixed table structure

Introduction to Redis:

Redis is a key-value storage system,

The data type of key contains: Strings,hashes,lists,set (collection), Zset (ordered collection)

To ensure efficiency, the data is cached in memory and can be stored periodically on disk.

The appropriate scenarios for Redis:

1. The application directly reads and writes to the Redis server cluster.

2. Application read-write Redis,redis and MySQL synchronization, the application can also read and write Mysql,redis problems, no impact

Redis is easy to do for those scenarios:

1. Take the latest N data operation

2. Leaderboard application, take TOPN operation

3. Applications that need to set the expiration time accurately

4. Counter Application

5.Uniq operation to get all data discharge values for a certain period of time

6. Real-time system, anti-spam system

7.pub/sub Building a real-time messaging system (publish subscription)

8. Build a queue system

9. Caching

The difference between Redis,mysql,mogodb:

Redis,mongodb and MySQL have a library concept.

Redis has no tables, MySQL has tables, MONGO collection

Redis has no fields, MySQL has fields, and MONGO has no

Adaptive Scenarios for Redis