Data that is frequently read and rarely changed can be placed in the cache. Data with high performance requirements needs to be updated in the cache at the same time as the database. If the requirements are not high, let the cache expiration strategy be tossed by yourself.
Shouldn’t we first look at the interface access speed and then decide whether caching is necessary? If your table is optimized well enough and the interface is fast enough, why should you use cache?
Data that is frequently read and rarely changed can be placed in the cache.
Data with high performance requirements needs to be updated in the cache at the same time as the database. If the requirements are not high, let the cache expiration strategy be tossed by yourself.
I am used to storing it in the cache, but remember to modify the data in the cache when modifying user information
Shouldn’t we first look at the interface access speed and then decide whether caching is necessary? If your table is optimized well enough and the interface is fast enough, why should you use cache?