Dutch cloud. Human support.

Hosting for Webshops: Magento, WooCommerce and Shopware

Hosting for Webshops: Magento, WooCommerce and Shopware

Your choice of e-commerce platform largely determines what hosting environment you need. WooCommerce, Magento and Shopware each have different requirements, and those requirements grow as your webshop grows.

Webshop hosting is a different discipline than regular website hosting. A product page with real-time stock information, a shopping cart that tracks session data, payment processes that need fast responses, pricing rules calculated across thousands of products: these are all demanding operations. And all of this while the site needs to stay fast, even under pressure.

The three most widely used open-source platforms in the Netherlands are WooCommerce (on WordPress), Magento (now Adobe Commerce) and Shopware. They target different market positions and have vastly different hosting requirements.

WooCommerce: lowest barrier, biggest pitfalls

WooCommerce powers more than a third of all webshops worldwide. The popularity makes sense: it runs on WordPress, is free, and you can go live within a day. But that low barrier to entry has a downside when it comes to performance.

WordPress was built as a CMS, not an e-commerce platform. WooCommerce adds shop functionality to it, but the PHP architecture and database model are not optimised for high concurrency or large product catalogues. Every page load generates multiple database queries. Without caching, that becomes a problem.

Minimum hosting requirements for WooCommerce:

  • PHP 8.1 or higher
  • MySQL 8.0 or MariaDB 10.6
  • At least 512 MB PHP memory (for larger shops, 1-2 GB is more realistic)
  • SSD storage (HDD is too slow for production environments)

For a small shop with a hundred products and limited traffic, good shared hosting or an entry-level VPS is sufficient. Once you exceed 10,000 product pages and more than a thousand orders per day, requirements become significantly more serious: Redis for object caching, a CDN for static assets, and at least 4 vCPUs and 8 GB RAM for the web server.

A critical point in WooCommerce hosting is the ratio of PHP workers to concurrent visitors. Every active PHP request blocks a worker. With few workers and many concurrent visitors, the queue fills up and load times increase. This is the most common mistake with WooCommerce on shared hosting.

Magento / Adobe Commerce: enterprise-grade

Magento was built for larger, more complex webshops. The platform supports multiple stores from a single installation, advanced pricing rules, B2B functionality and extensive product catalogues. That power comes at a cost: Magento has the highest requirements of the three platforms.

The average server response time of Magento is 824 milliseconds, higher than WooCommerce and Shopware. That is not necessarily a problem if you configure the platform correctly, but it shows that without additional measures you are already behind.

Minimum production requirements for Magento 2:

  • PHP 8.2 or 8.3
  • Elasticsearch or OpenSearch (required for search functionality)
  • Redis for session and page caching
  • Varnish as Full Page Cache (strongly recommended)
  • MySQL 8.0 or MariaDB 10.6
  • At least 8 GB RAM for a single server

Magento does not perform well on shared hosting or small VPS environments. The minimum sensible setup for production use is a dedicated server or cloud instance with sufficient memory. For large webshops, a cluster of multiple servers is almost always necessary.

The Adobe Commerce (Magento Enterprise) version has a licence fee on top of all that, typically tens of thousands of euros per year. For most Dutch webshops, the open-source Community Edition is the practical choice.

Hosting requirements compared

WooCommerce
Min. RAM: 4 GB
PHP workers: 10-20
DB: MySQL/MariaDB
Cache: Redis + CDN
Scale: small to medium
Lowest entry costs
Magento 2
Min. RAM: 8-16 GB
PHP-FPM: dedicated
DB + Elasticsearch
Cache: Varnish + Redis
Scale: medium to large
Highest server costs
Shopware 6
Min. RAM: 8 GB
PHP 8.2+ required
MySQL + Elasticsearch
Cache: Varnish + Redis
Scale: medium to enterprise
Modern architecture

Shopware: the European challenger

Shopware is built on the Symfony framework and has a more modern architecture than WooCommerce or Magento. The HTTP cache and Varnish integration are baked into the platform, which makes out-of-the-box performance better than the competition.

Shopware uses Elasticsearch for product searches and supports a fully headless setup via the Store API. That flexibility makes it interesting for retailers who want to go beyond a standard webshop, but the hosting requirements match accordingly:

  • PHP 8.2 or higher (Symfony 7.x)
  • MySQL 8.0 or MariaDB 10.11
  • Elasticsearch 8.x or OpenSearch 2.x
  • Redis for sessions and cache
  • At least 8 GB RAM

Shopware is relatively new as a serious option in the Netherlands, but gaining ground. Especially in the mid-market (webshops with 1 to 50 million euros in revenue), the platform is strongly represented.

Session handling: the underestimated problem

A problem that affects all three platforms: session storage. In a standard configuration, PHP stores sessions in files on the server. With one server, this works. With a cluster of multiple web servers, it does not: visitor X may land on server A with their shopping cart, but their next request goes to server B, which does not know the session.

The solution is centralised session storage in Redis. Redis is an in-memory key-value store that is extremely fast and can be used by all application servers simultaneously. Redis drivers are available for WooCommerce, Magento and Shopware, and in most cases also recommended as the standard configuration.

This is one of the first things you configure when expanding from a single server to a cluster.

Hosting advice by webshop size

Starter
0-500k revenue / <100 orders/day - Managed VPS (4 vCPU, 8 GB) + Redis + CDN
Growth
500k-5M / 100-1000 orders/day - Dedicated server or cloud (8 vCPU, 16-32 GB) + Redis + Varnish + DB replica
Scale-up
5-50M / 1000+ orders/day - Cloud cluster (load balancer + 3+ web servers + dedicated DB) + auto-scaling
Enterprise
50M+ - Microservices, multi-region, dedicated infra team, SLA with 99.99% uptime

Caching is the difference between a slow and a fast webshop

All three platforms have extensive caching capabilities, but they are not well-configured by default. That is work that needs to be done when setting up the hosting environment.

For WooCommerce, plugins like W3 Total Cache or WP Rocket are common, but for serious shops Redis object caching via the PHP extension is the better choice. For Magento and Shopware, Varnish as Full Page Cache is the standard in production environments, and that configuration is not trivial.

A well-configured caching layer can reduce database load by 80 to 90 percent. That is directly visible in response times and in the amount of server capacity you need.

Conclusion

Choosing WooCommerce, Magento or Shopware is not just a platform choice, it is also an infrastructure choice. WooCommerce has the lowest barrier to entry but requires attention as you grow. Magento is powerful but needs serious resources from day one. Shopware sits in between with a modern foundation.

Whichever platform you choose: invest early in Redis, a CDN and a good caching configuration. That investment pays off in speed, scalability and lower server costs in the long run.

Looking for the right hosting for your webshop? Explore our e-commerce solutions.

Need help with implementation?

Our experts are happy to provide personal advice.

Schedule a call