


[Cache Design] Is the most basic multi-level cache suitable and how should it be set up?
Recently, we want to build a level-one caching mechanism for our system. But I always feel like something is missing.
Environment:
Load balancing, master-slave separation, Redis standalone (can be multiple machines in the future)
Now the initial idea:
<code>浏览器缓存-》本地文件缓存-》内存缓存(Redis)-》Db </code>
After the user accesses the web application, set the browser cache for it, and then set the local file cache and memory cache.
After other users visit, I think the steps are as follows:
Check if there is browser cache
Retrieve whether the local machine has a file cache
Memory cache
Db
My question is:
But I feel that something is missing in a certain step, or I feel that the (multi-level) cache expiration time is difficult to choose.
Also, is the local file cache {checking expiration time, reading (deleting, generating) files} worth it compared to a single connection that jumps directly to the memory cache (Redis)?
So I would like to consult my basic caching mechanism to see if it is suitable or if there are any shortcomings that can be improved. Thank you!
Reply content:
Recently, we want to build a level-one caching mechanism for our system. But I always feel like something is missing.
Environment:
Load balancing, master-slave separation, Redis standalone (can be multiple machines in the future)
Now the initial idea:
<code>浏览器缓存-》本地文件缓存-》内存缓存(Redis)-》Db </code>
After the user accesses the web application, set the browser cache for it, and then set the local file cache and memory cache.
After other users visit, I think the steps are as follows:
Check if there is browser cache
Retrieve whether the local machine has a file cache
Memory cache
Db
My question is:
But I feel that there is something missing in a certain step, or I feel that the (multi-level) cache expiration time is difficult to choose.
Also, is the local file cache {checking expiration time, reading (deleting, generating) files} worth it compared to a single connection that jumps directly to the memory cache (Redis)?
So I would like to consult my basic caching mechanism to see if it is suitable or if there are any shortcomings that can be improved. Thank you!
Multi-level cache can reduce the pressure on the system and greatly reduce RT. However, one aspect that needs to be considered is the management of multi-level cache. This is also mentioned by the author in the article. This is avoided by using multi-level cache. Can't solve the problem. As for how to invalidate multi-level cache, you can try to use a local timer to refresh the cache at intervals
In fact, the file cache can be replaced by a local memory cache. It is also possible to design it as a file cache. However, when the volume of local disk I/O is large, I am afraid that it cannot handle it. As for which one is more efficient and network overhead, it needs to be based on the actual situation. Go and take a pressure test
Multi-level caching is more about cache penetration and program robustness. When there is a problem with the centralized cache, our application can continue to run; some hot data is made into a memory cache, so there is no need to access the centralized cache. , which can reduce the pressure on centralized cache. So in this aspect, file caching is better than Redis’s centralized caching

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

PHP and Python each have their own advantages, and choose according to project requirements. 1.PHP is suitable for web development, especially for rapid development and maintenance of websites. 2. Python is suitable for data science, machine learning and artificial intelligence, with concise syntax and suitable for beginners.

PHP is a scripting language widely used on the server side, especially suitable for web development. 1.PHP can embed HTML, process HTTP requests and responses, and supports a variety of databases. 2.PHP is used to generate dynamic web content, process form data, access databases, etc., with strong community support and open source resources. 3. PHP is an interpreted language, and the execution process includes lexical analysis, grammatical analysis, compilation and execution. 4.PHP can be combined with MySQL for advanced applications such as user registration systems. 5. When debugging PHP, you can use functions such as error_reporting() and var_dump(). 6. Optimize PHP code to use caching mechanisms, optimize database queries and use built-in functions. 7

PHP remains important in modern web development, especially in content management and e-commerce platforms. 1) PHP has a rich ecosystem and strong framework support, such as Laravel and Symfony. 2) Performance optimization can be achieved through OPcache and Nginx. 3) PHP8.0 introduces JIT compiler to improve performance. 4) Cloud-native applications are deployed through Docker and Kubernetes to improve flexibility and scalability.

PHP is suitable for web development, especially in rapid development and processing dynamic content, but is not good at data science and enterprise-level applications. Compared with Python, PHP has more advantages in web development, but is not as good as Python in the field of data science; compared with Java, PHP performs worse in enterprise-level applications, but is more flexible in web development; compared with JavaScript, PHP is more concise in back-end development, but is not as good as JavaScript in front-end development.

PHP is still dynamic and still occupies an important position in the field of modern programming. 1) PHP's simplicity and powerful community support make it widely used in web development; 2) Its flexibility and stability make it outstanding in handling web forms, database operations and file processing; 3) PHP is constantly evolving and optimizing, suitable for beginners and experienced developers.

PHP is used to build dynamic websites, and its core functions include: 1. Generate dynamic content and generate web pages in real time by connecting with the database; 2. Process user interaction and form submissions, verify inputs and respond to operations; 3. Manage sessions and user authentication to provide a personalized experience; 4. Optimize performance and follow best practices to improve website efficiency and security.

PHP and Python each have their own advantages and are suitable for different scenarios. 1.PHP is suitable for web development and provides built-in web servers and rich function libraries. 2. Python is suitable for data science and machine learning, with concise syntax and a powerful standard library. When choosing, it should be decided based on project requirements.

The reasons why PHP is the preferred technology stack for many websites include its ease of use, strong community support, and widespread use. 1) Easy to learn and use, suitable for beginners. 2) Have a huge developer community and rich resources. 3) Widely used in WordPress, Drupal and other platforms. 4) Integrate tightly with web servers to simplify development deployment.
