At the core for me. 1. Persistence is already very mature, 2.io performance is impressive, 3. The simple k-v structure can be combined to create various data structures, such as documents, trees, graphs, and networks 4. It’s so comfortable to be able to set up a life cycle for data
The data runs cutely in the memory. Anyway, you can be willful if you have money.
It cannot replace mysql. First, it does not have the functions of SQL and has no concept of relationships. Second, its data persistence and transaction management functions are far inferior to mysql. It can currently replace the simpler memcache as a cache server with a variety of data structures.
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
At the core for me.
1. Persistence is already very mature,
2.io performance is impressive,
3. The simple k-v structure can be combined to create various data structures, such as documents, trees, graphs, and networks
4. It’s so comfortable to be able to set up a life cycle for data
The data runs cutely in the memory. Anyway, you can be willful if you have money.
It cannot replace mysql. First, it does not have the functions of SQL and has no concept of relationships. Second, its data persistence and transaction management functions are far inferior to mysql. It can currently replace the simpler memcache as a cache server with a variety of data structures.
The previous location of program and database
Redis is not very reliable as a database
1. Too few supported data types
2. The query function is too weak
3. Data is not stored to disk in real time
Mainly cache some data that needs to be accessed frequently
Most websites now don’t require frequent logins. Generally, sessions are stored in the database. I only use redis for this job
A queue to save hot data