Use case · Ecommerce

Cluster hosting for Shopware and Magento

In brief

Shopware cluster hosting and Magento cluster hosting from managed-cluster.net run your store on several PHP-FPM app nodes behind redundant load balancers, with a replicated MySQL/MariaDB database, Redis, OpenSearch and HTTP caching. We operate it 24/7, checking the home page, search and checkout as a customer would. Your agency or team owns store code and plugins. From €449.99 net per month.

Architecture

Ecommerce cluster hosting, layer by layer

A shop cluster splits your store into layers. Redundant load balancers and an HTTP cache accept requests, PHP-FPM app nodes render pages, and the database, Redis, search and message queues run as separate services. The load balancers and app tier do not hinge on one server, the database is replicated, and we scale the app tier up before planned campaigns.

Diagram 01 Shop cluster: layers and data paths
  • Requests
  • Data paths to the database and services
  • external or separate from production
  • App node active
Diagram of a shop cluster for Shopware 6 or Magento 2. We define in the design how many app nodes your store needs and how each service is sized.
Diagram as text
  1. Customers reach the store through redundant load balancers.
  2. The HTTP cache (Varnish) answers repeat page requests and passes everything else on to the app nodes.
  3. Several app nodes running PHP-FPM handle dynamic requests. Before planned campaigns, we scale this tier up.
  4. Underneath run the database (MySQL or MariaDB with replication), Redis for sessions and caches, search (OpenSearch or Elasticsearch) and message queues with queue workers.
  5. Media are offloaded. A separate staging environment is available for deployments and store updates.
  6. 24/7 monitoring checks the home page, search and checkout from the customer's side.

One building block of high availability Magento hosting, and of any resilient Shopware setup, is an app tier that does not hinge on one server. If an app node fails, the app tier stays available: the load balancer removes the node from rotation within seconds, the remaining app nodes keep serving requests, and existing connections are re-established. Because sessions live in Redis, any app node can handle any request.

The database runs on MySQL or MariaDB with replication. Replication keeps the data current on more than one database server, but it also copies mistakes such as accidentally deleted data, and an HA cluster is no substitute for backups. Our page on automatic failover in a high availability cluster explains how quorum, fencing and failover work together.

Stack · Shopware 6

Shopware cluster hosting: the Shopware 6 stack

For Shopware 6 hosting in Germany, we run PHP-FPM app nodes with OPcache, MySQL or MariaDB with replication, Redis for sessions and caches, OpenSearch or Elasticsearch, message queues with queue workers, and Varnish or an HTTP cache. The table shows what role each component plays according to the Shopware documentation and what we take care of in operations.

Shopware 6 Components in the shop cluster
ComponentRole in Shopware 6What we operate
PHPApplication runtime; Shopware requires PHP 8.2 or later and recommends 8.4Several PHP-FPM app nodes behind redundant load balancers, OPcache tuning
DatabaseRequired; Shopware lists MariaDB 10.11.6 or later and MySQL 8.0.22 or laterMySQL or MariaDB with replication, database tuning
HTTP cacheReverse HTTP cache in front of the store; the documentation covers Varnish and FastlyVarnish or HTTP cache in front of the app nodes
Message queueThe default transport stores messages in the database, which Shopware does not recommend for production; messages should be processed by CLI workersMessage queues with queue workers, worker tuning
SearchOpenSearch or Elasticsearch for product search and indexing, optional according to ShopwareElasticsearch/OpenSearch on the cluster
Sessions and cacheRedis 7 or later, or Valkey (8.0 recommended), for caching and session storage; optional according to ShopwareRedis for sessions and caches
MediaProduct images and store filesOffloaded media

Vendor information for Shopware 6.7 from the Shopware documentation (sources 1 to 3), as of . The components we deploy are listed in the component list of your design.

Stack · Magento 2

Magento cluster hosting: the Magento 2 stack

For Magento 2, we run the same layers with two priorities: Varnish as the full-page cache in front of the app nodes, and a search engine, which Adobe has required since Magento 2.4.0. We also tune indexers and queue workers. For enterprise Magento 2 hosting, the Enterprise package adds separate networks, VPN, IP whitelisting and role-based access.

Magento 2 Components in the shop cluster
ComponentRole in Magento 2What we operate
Full-page cacheAdobe's documentation highly recommends Varnish; the built-in page cache module is meant for development onlyVarnish in front of the app nodes, behind redundant load balancers
SearchRequired since 2.4.0, when MySQL search was removed; the system requirements list OpenSearch for 2.4.9 and OpenSearch or Elasticsearch 8 for 2.4.8Elasticsearch/OpenSearch on the cluster
IndexersPrepare catalog data; since 2.4.8, new indexers default to “Update by Schedule” modeIndexer tuning in day-to-day operations
PHPApplication runtimeSeveral PHP-FPM app nodes, OPcache tuning
DatabaseMySQL or MariaDBReplication, database tuning
Message queuesAsynchronous processing of tasksMessage queues with queue workers
Sessions and cacheShared storage for all app nodes; Adobe recommends Redis for multi-node setups, while the current system requirements list ValkeyShared session and cache storage for all app nodes

Vendor information from Adobe's Magento documentation (sources 4 to 7), as of . Versions and recommendations change with each release. The components your shop cluster uses are listed in the component list of your design.

Sources

  1. Shopware AG: Shopware Documentation, “Hosting” (recommended stack and supported versions). developer.shopware.com, retrieved October 9, 2026.
  2. Shopware AG: Shopware Documentation, “Reverse HTTP Cache”. developer.shopware.com, retrieved October 9, 2026.
  3. Shopware AG: Shopware Documentation, “Message Queue”. developer.shopware.com, retrieved October 9, 2026.
  4. Adobe: Experience League, “Software Recommendations” (performance best practices). experienceleague.adobe.com, retrieved October 9, 2026.
  5. Adobe: Experience League, “Magento Open Source 2.4.0 release notes”. experienceleague.adobe.com, retrieved October 9, 2026.
  6. Adobe: Experience League, “System Requirements”. experienceleague.adobe.com, retrieved October 9, 2026.
  7. Adobe: Experience League, “Magento Open Source 2.4.8 release notes”. experienceleague.adobe.com, retrieved October 9, 2026.

Responsibilities

Who is responsible for what in a shop cluster

We are responsible for your store's platform: operating system, services, security, backups and performance. The store code, plugins and store updates stay with your agency or in-house team. Staging, deployments and performance analysis are joint work. The table shows what this split means in day-to-day operations.

Who does what How tasks are split between us, your agency and your team
AreaResponsibleWhat it means for your store
Operating system and servicesUsPHP-FPM, database, Redis, search, message queues and HTTP cache. We apply updates node by node while your systems keep running. Exceptions such as a major database upgrade are announced in advance and scheduled in a window you choose.
Platform securityUsSecurity patches for the operating system and services, with critical vulnerabilities first. Hardening with minimal services, restrictive firewalls and secured SSH access.
BackupsUsBackups run on infrastructure separate from the cluster, with defined retention periods and regular restore tests. Our page on backups with restore tests shows how we back up and restore.
Platform performanceUsTuning of OPcache, indexers, queue workers and the database.
Monitoring and on-call dutyUs24/7 monitoring across every layer, plus checks from the customer's perspective on the home page, search and checkout. Critical alerts reach on-call duty immediately and are handled right away, around the clock.
StagingJointWe provide the staging environment, where deployments and store updates can be checked before they go live.
DeploymentsJointYour agency delivers the code, and we support the deployment to the cluster.
Performance analysisJointWhen there is a bottleneck, we work with your agency to find out whether the cause lies in the platform or in the store.
Store code and pluginsAgency or your teamDevelopment, extensions and plugins for your store.
Store updatesAgency or your teamNew Shopware or Magento releases and their plugins.

You have a dedicated contact who knows your cluster. If an agency works on your store, we coordinate staging, deployments and performance questions directly with them.

Load peaks

Handling traffic peaks such as Black Friday

A shop cluster absorbs traffic peaks in three ways. The HTTP cache answers repeat page requests before they reach the app nodes. Several app nodes share dynamic requests such as cart, search and checkout. Before planned campaigns, we scale the app tier up and scale it back down once the campaign is over.

  1. CAMPAIGN PLANNED. You tell us the date and type of promotion, for example a newsletter, a TV spot or Black Friday.
  2. We scale up the app tier before the start.
  3. During the campaign, 24/7 monitoring checks the home page, search and checkout from the customer's side.
  4. After the campaign, we scale the app tier back down.

Sequence before planned campaigns; headroom for peak loads and growth is defined in the design.

The basis is sizing: we discuss the hardware of the cluster nodes (CPU, RAM, storage, network) individually and define it in the design proposal, with headroom for peak loads and growth.

In ongoing operations, capacity planning shows us trends early. Your monthly operations report covers availability, incidents and utilization, along with our recommendations for expansion.

Migration

Store migration: build in parallel, switch over under control

A store migration takes four steps: an analysis of your current environment, building the cluster in parallel, migrating data and media, and switching over in a low-traffic window with a rollback plan. Because the cluster is built alongside your current setup, your store keeps running there until the switchover. You choose the date.

  1. 1

    Analysis

    We review your store, load profile and availability and recovery targets. If your store runs an older version, we discuss an upgrade path. The result is a written design with a fixed price.

  2. 2

    Parallel build

    The cluster is built next to your current environment, including staging, monitoring and backups. Before handover, we test failover.

  3. 3

    Data and media

    We migrate the database and media files to the cluster.

  4. 4

    Switchover

    The switchover takes place in a low-traffic window on a date you set. A rollback plan defines the way back if anything does not go as planned.

Two sites

Shop clusters across two data centers

Protection against the loss of an entire data center requires a second site. The Business package spreads six nodes across FRA01 and NBG01. It includes Ceph HA storage replicated across both sites, backups with restore tests at the second site and a documented switchover plan that is tested regularly. The Enterprise package provides a multi-site architecture designed to your requirements.

Whether your store needs a second site depends on your availability target, which we define together. NBG01 in Nuremberg holds backup copies outside the primary site and is the second location for multi-site deployments, as described under our second site, NBG01. For scope and price, see the Business package with six nodes across two sites.

Pricing

Pricing for shop clusters

Shop clusters use our standard package pricing. Essentials, the starting point for production Shopware and Magento stores, costs €449.99 net per month. Business with six nodes across two sites costs €1,099.99 net per month.

We price Enterprise environments by data volume, recovery point objective (RPO) and switchover time and state the fixed price in the proposal.

Compare managed Proxmox cluster packages

Essentials · Ceph HA

€449.99 / month, net

The starting point for production Shopware and Magento stores.

  • 3 nodes with quorum
  • Ceph HA storage: three-way replication, self-healing
  • 24/7 monitoring and alerting, including checkout checks
  • Fully managed, including updates
  • Network-level DDoS protection
Request a shop cluster with Essentials

All prices are net, plus VAT. As of .

FAQ

Frequently asked questions about shop clusters

Which Shopware and Magento versions do you support?

Shopware 6 and Magento 2, each with the usual stack of PHP-FPM, MySQL or MariaDB, Redis, OpenSearch or Elasticsearch and message queues. We also run older versions, and in that case we talk with you about an upgrade path.

Who handles plugins and store updates?

Your agency or your in-house team. We are responsible for the platform underneath: operating system, services, security, backups and performance. For store updates, we provide a staging environment and support the deployment.

Will you work with our agency?

Yes. We coordinate directly with your agency or development team and provide staging, deployment support and performance analysis. For the infrastructure, you have a dedicated contact who knows your cluster.

How do you handle traffic peaks?

With an HTTP cache, several app nodes and planned scaling. Before planned campaigns, we scale the app tier up and back down afterwards. Headroom for peak loads and growth is already part of the sizing in the design.

Can a shop cluster run across two sites?

Yes, with the Business package: six nodes spread across FRA01 and NBG01, with Ceph HA storage replicated across both sites and backups with restore tests at the second site. The Enterprise package provides a multi-site architecture designed to your requirements.

How much does a shop cluster cost?

From €449.99 net per month for the Essentials package with three nodes and Ceph HA storage. All packages and services are compared on our managed Proxmox cluster pricing page.

Next step

Which cluster fits your store?

Tell us your platform and version, key extensions, typical traffic peaks and your availability target. You receive a written design with an architecture diagram, a component list and a fixed price for setup and operations.

Discuss a shop cluster

Related