Web
- Enable scale of nodes for traffic and redundancy
- One node is master and runs cron
- Alternatively, use a dedicated Admin and worker nodes
Cache
- Consider implementing a separate Redis instance for sessions
- You can have a Redis instance per cache
- Size your instance to contain the largest expected cache size
Database and queues
- High-traffic sites can tune DB performance with slave DBs and split DBs for orders/carts (in Adobe Commerce)
- Consider using a slave DB to enable quick recovery and for data backups
- Low-traffic sites can store images in the DB
Search
- Tune the number of instances based on search traffic
Storage
- Consider using GFS or GlusterFS for pub/media storage
- Alternatively, use DB storage for low-traffic sites
Recommended Varnish reference architecture
Magento supports several full page caching engines (File, Memcache, Redis, Varnish) out of the box, along with expanded coverage through extensions. Varnish is the recommended full page cache engine. Commerce supports many different Varnish configurations.
For sites that do not require high availability, we recommend using a simple Varnish setup with Nginx SSL termination.
For sites that require high availability, we recommend using a 2-tier Varnish configuration with an SSL terminating load balancer.
Previous pageSoftware recommendations
Next pageDevelopment environment