Magento hosting, now Adobe Commerce and the open-source Magento Open Source, requires more resources than most e-commerce platforms. Magento's flexibility comes with heavy PHP processing, a demanding database, search services and background processes. Stores running Magento need dedicated resources, careful tuning and solid security to provide fast shopping experiences.
Why Magento needs more resources
Magento uses a complex architecture with many modules, an EAV database model and extensive indexing. Recent versions require OpenSearch or Elasticsearch for catalogue search, Composer for installation and cron jobs for indexing, emails and scheduled operations. Redis is strongly recommended for cache and sessions. This stack does not fit well on shared hosting, so most Magento stores run on a VPS or dedicated server.
- PHP version supported by your Magento release
- MySQL or MariaDB with sufficient memory
- OpenSearch for catalogue search
- Redis for cache and sessions
- Varnish for full-page caching
Performance tuning
Run Magento in production mode, enable all caches and use Varnish for full-page caching. Configure Redis for cache and session storage. Set indexers to update on schedule and ensure cron runs reliably. Optimise images, enable JavaScript bundling or modern build tools and use a CDN for media. Plan enough RAM for PHP-FPM, MySQL, OpenSearch and Redis together, and use NVMe storage.
Security for Magento stores
Magento stores are high-value targets. Apply security patches promptly, use two-factor authentication for admin accounts, change the admin URL and restrict access by IP when possible. Use payment integrations that keep card data off your server. Monitor file integrity and run malware scans. Keep daily backups of the database and media.
Scaling for growth
Larger stores separate services across servers: database, search, cache and web nodes. Load testing before sales events helps identify bottlenecks. Dedicated servers provide consistent performance for high-volume stores.
Development and deployment
Use Git and Composer, maintain staging environments and deploy with tools such as Deployer to minimise downtime during updates. Compile static content and generated code during the build step, not on the live server.
Choosing a plan
Small Magento stores need at least a mid-range VPS with plenty of RAM. Busy stores should consider dedicated servers. Compare RAM, CPU and storage in the plans below.