Depends on the scenario, redis seems to be able to persist, although I don’t know if it can have the reliability of a relational database Complex logic must be uploaded to the database
To compare whether it can be replaced, we need to find out three important points: 1. There are still problems with Redis data persistence. 2. Strict transaction ACID is not supported 3. Complex condition queries are not supported.
In the production environment, redis is mostly used for cache or queue, and data storage still needs to be placed in a relational database such as mysql
Redis is generally used for caching. If you need persistent storage, you will definitely need a database like mysql
Depends on the scenario, redis seems to be able to persist, although I don’t know if it can have the reliability of a relational database
Complex logic must be uploaded to the database
Must be required. nosql is not suitable for all development scenarios.
And the persistence of redis is not absolutely perfect
http://blog.jobbole.com/83459/
I recommend reading this!
To compare whether it can be replaced, we need to find out three important points:
1. There are still problems with Redis data persistence.
2. Strict transaction ACID is not supported
3. Complex condition queries are not supported.
Front-end reads data from redis
Backend operations use mysql
Backend mysql synchronizes to redis
Front-end redis data queue to mysql
Required.
In the production environment, redis is mostly used for cache or queue, and data storage still needs to be placed in a relational database such as mysql
That’s necessary
Redis is a cache, and the cache is not a place for persistence. The database is
Persistence is necessary