Configure caching
- Topics:
- Configuration
- Cache
CREATED FOR:
- Experienced
- Admin
- Developer
Commerce enables you to configure alternatives to the default file system caching. This guide discusses some of those alternatives; namely,
Caching terminology
Commerce uses the following caching terminology:
-
Frontend—Similar to an interface or gateway to cache storage, implemented by Magento\Framework\Cache\Frontend.
-
Cache types—Can be one of the types provided with Commerce or you can create your own.
-
Backend—Specifies details about cache storage, implemented by Magento\Framework\Cache\Backend
-
Two-level backend—Stores cache records in two backends: a faster one and a slower one.
INFO
Two-level backend cache configuration is beyond the scope of this guide.
Configuration options
-
Modifying the provided
default
cache frontend—You modify only the
<magento_root>/app/etc/di.xml
file, the Commerce application’s global dependency injection configuration. -
Configuring your own custom cache frontend—
You modify only the
<magento_root>/app/etc/env.php
file because it overrides the equivalent configuration in thedi.xml
file.
Commerce
- Overview
- General setup
- Deployment
- Cache
- Command Line
- Command-line tool
- Common commands
- Enable logging
- Manage the cache
- Manage indexers
- Configure cron jobs
- Compile code
- Operation mode
- Start message queue consumers
- URN highlighter
- Dependency reports
- Localization
- Configuration management
- Static view
- Create symlinks
- Run unit tests
- Convert layout files
- Generate data for performance testing
- Run support utilities (Commerce only)
- Configuration files
- Configuration paths
- Cron Jobs
- Logs
- Message Queues
- Multiple sites
- Search Engine
- Security
- Storage
- Return to Operational Guides