Skip to main content

How caching is used in Magento

What is Caching?

In computing, a cache is a high-speed data storage layer that stores a subset of data, typically transient in nature, so that future requests for that data are served up faster than is possible by accessing the data’s primary storage location. Caching allows you to efficiently reuse previously retrieved or computed data.

How caching is implemented in Magento?

The Magento page cache library contains a simple PHP reverse proxy that enables full page caching out of the box. A reverse proxy acts as an intermediary between visitors and your application and can reduce the load on your server.

Magento's default caching mechanism provides different storage options that store cached data in 3 different sources:

  • File System
  • Database
  • Redis
There are different types of cache available by default in Magento. You can check here about different types.

Any page new page added to the website is by default cachable. But a developer can make any page uncacheable by adding a small chunk of code in the page layout file.

<block cacheable="false" class="Magento\Customer\Block\Form\Edit" name="customer_edit" template="Magento_Customer::form/edit.phtml">
    <container as="form_additional_info" name="form.additional.info">
</container></block>

NOTE: A developer should always take care that this code should not be added in the default.xml file or any other layout file which is added across the website. Because this code is added in the layout, then that makes the complete page uncacheable.

Different Cache Commands

Magento has provided different commands to execute different cache operations. They are below:

  1. php bin/magento cache:status: This command is used to check the status of the individual cache types.
  2. php bin/magento cache:enable: This command is used to enable the cache. You can pass cache type as parameter in the command as below:
    php bin/magento cache:enable [type] ... [type]
  3. php bin/magento cache:disable: This command is used to disable the cache. You can pass cache type as parameter in the command as below:
    php bin/magento cache:disable [type] ... [type]
  4. php bin/magento cache:clean: This command is used to clear the cache. You can pass cache type as parameter in the command as below:
    php bin/magento cache:clean [type] ... [type]
  5. php bin/magento cache:flush: This command is used to remove the cache. You can pass cache type as parameter in the command as below:
    php bin/magento cache:flush [type] ... [type]

NOTE: The type option is a space-separated list of cache types.

Difference Between Cache Clean & Cache Flush

  • Cache Clean: This command deletes all the enabled magento related cache. And does not impact the other stored data in the same storage.
  • Cache Flush: This command deletes all the magento related cache and also delete all the other stored data in the same storage. This might impact the other applications which are using the same storage for caching.

Comments

Popular posts from this blog

Unlocking Success: The Vital Role of the Contact Us Page in E-commerce

In the dynamic realm of e-commerce, where digital transactions reign supreme, the significance of customer communication cannot be overstated. Amidst the plethora of factors influencing the success of an online store, one often overlooked yet fundamentally important element is the Contact Us page. This seemingly humble corner of a website holds immense power, serving as a linchpin in fostering trust, resolving issues, and nurturing customer relationships. Let's delve deeper into why the Contact Us page is not just an afterthought but a strategic asset for e-commerce businesses, backed by proven data. Building Trust and Credibility Trust is the cornerstone of any successful e-commerce venture. According to a survey conducted by Edelman, 81% of consumers say that trusting a brand to do what is right is a deciding factor in their purchasing decisions. A prominently displayed Contact Us page with clear contact information, including a physical address, phone number, and email address, ...

Magento - LogRocket Integration

In today’s competitive eCommerce landscape, understanding user behavior is crucial for optimizing customer experiences and improving conversion rates. Magento 2, a powerful and flexible eCommerce platform, allows merchants to customize their online stores extensively. However, monitoring how users interact with these customizations is often challenging. This is where LogRocket, a modern session replay tool, comes into play. Integrating LogRocket with Magento 2 can provide invaluable insights into user behavior, performance bottlenecks, and UX issues. In this blog post, we’ll walk you through the steps to integrate LogRocket with Magento 2, and how this integration can help you improve your store’s performance and user experience. What is LogRocket? LogRocket is a session replay tool that enables you to record and playback user activity on your website. It tracks interactions such as clicks, scrolls, and form inputs, giving you a clear view of how users navigate your store. In addition,...

Using Composer Update is a Crime: Why Magento Developers Should Avoid It

As a Magento developer, managing third-party modules via Composer is essential for keeping your project organized and up to date. However, when installing a new module, there’s one command that might seem tempting, yet can lead to chaos if not used carefully: composer update Yes, you read that right—using composer update can be a crime (against your project, that is). In this blog, we’ll explore why running composer update without caution can be risky, and why you should think twice before pulling the trigger. Let’s break it down. What Does composer update Do? At first glance, composer update seems harmless. When you run it, Composer checks for newer versions of every package listed in your composer.json file and updates them to the latest compatible versions based on your version constraints. That sounds good, right? Why wouldn't you want the latest updates? Well, here's where things get tricky. The Hidden Risk of composer update Running composer update doesn't just u...