Evolution of large website architectures (3) Use cache to improve website performance and Architecture Evolution

Evolution of large website architectures (3) Use cache to improve website performance and Architecture Evolution

Website access also follows the 80% law: 20% of business access is concentrated on 20% of the data. If we cache of the data, can we reduce the access pressure on the database? During project development, we usually cache some basic information, such as country, city, airline, airport and terminal information in the Business Travel System.

Use cache to improve website performance

Cache is generally divided into two types: local cache and distributed cache. Local cache refers to the local cache of the application server, and distributed cache refers to specialized cache servers, such as memcached and redis. Is the architecture of the website after the cache is used:

 

Conclusion: After the cache is used, the read Pressure on the database is reduced, but the problem persists: the number of requests that an application server can process is limited. When the concurrent access volume increases, the application server will become the performance bottleneck of the entire website.