Multi-Region Packages

Multi-Region WordPress Packages

On Virtuozzo Application Management installations with multiple availability zones, specialized WordPress packages can deploy standalone or clustered WordPress environments across several regions. This creates a distributed WordPress solution that can better handle high traffic and improve performance for users in different geographical locations.

Multi-Region WordPress Standalone

The Multi-Region WordPress Standalone package installs two WordPress Standalone instances in different regions and connects them into one multi-region WordPress solution.

Multi-region WordPress standalone schema
Two WordPress Standalone environments are connected across separate regions.
  1. Open Marketplace, find the Multi-Region WordPress Standalone package, and click Install.
  2. Select the required advanced features:
    • LiteSpeed High-Performance Web Server instead of the default NGINX web server
    • Brute Force Attack Protection and Web Application Firewall for LiteSpeed
    • Let’s Encrypt SSL with Auto-Renewal
  3. Select two regions and start the installation.
  4. Wait while both WordPress Standalone environments are created and configured automatically.
Multi-region WordPress standalone installation
Configure the Multi-Region WordPress Standalone installation options and regions.
Multi-region WordPress standalone environments
The deployment creates two interconnected WordPress Standalone environments in separate regions.

After deployment, the success message and email contain the administration-panel URLs and access credentials. By default, the first environment is the primary and the second is the replica.

A custom domain can be assigned to the primary environment. For a geo-distributed WordPress solution, attach public IP addresses to both environments and configure DNS load balancing to distribute traffic between them.

Multi-Region WordPress Cluster

The Multi-Region WordPress Cluster package deploys multiple WordPress Cluster instances in different regions and connects them into one multi-region WordPress solution. The exact architecture depends on the selected database topology.

Database Topologies

Async Primary-Replica Distribution

This option requires at least two regions. Two primary database servers are connected using asynchronous replication. The primary in the first region handles read and write requests, while the primary in the second region handles reads. If the first primary becomes unavailable, the second begins accepting writes. With more than two regions, the additional regions use replica database servers.

  • Suitable when read operations greatly exceed write/update operations.
  • Suitable when inter-region latency is more than a few tens of milliseconds.
  • Suitable when replication transaction time is not critical and can be longer than in a single cluster.
Async Primary-Replica WordPress cluster
Async Primary-Replica Distribution across WordPress cluster regions.

Sync Galera Distribution

This option requires at least three regions. MariaDB Galera uses a multi-data-center topology with cluster members grouped into segments across different regions. Its multi-primary topology and automatic node provisioning are intended to provide synchronized data across regions and avoid lost transactions when a node fails.

  • Suitable when data must be available in every region immediately after the transaction completes.
  • Suitable when latency between regions is very low.
Sync Galera WordPress cluster
Sync Galera Distribution across multiple WordPress cluster regions.
Topology selection: the source recommends measuring latency between regions. If the average ping time is below 20 ms for all regions, Sync Galera Distribution can be used. Otherwise, Async Primary-Replica Distribution is recommended.

GlusterFS Shared Storage

The package uses a GlusterFS Cluster as fault-tolerant shared storage for static assets. Each independent server stores its own copy of the data, which allows WordPress to read from any copy and helps distribute read load.

Data is synchronized between regions through GlusterFS Geo-Replication. The storage architecture uses a Primary-Replica model where one GlusterFS cluster acts as primary and accepts write operations.

WordPress multi-region GlusterFS schema
GlusterFS Geo-Replication synchronizes static assets between regions.

Because Virtuozzo Application Management transparently interconnects available regions at the environment level as if they were on the same LAN, the GlusterFS Geo-Replication Local Area Network deployment scenario is used.

Multi-Region WordPress Cluster Installation

  1. Open Marketplace, find the Multi-Region WordPress Cluster package, and click Install.
  2. Configure the installation options:
    • Database Topology — select Async Primary-Replica or Sync Galera.
    • Regions — at least two for Async; at least three for Sync Galera.
    • Environment — specify the multi-region WordPress cluster environment name.
    • Scaling Strategy — choose according to the expected load.
    • Advanced Features — configure the required package features.

The source lists these advanced feature options for the multi-region cluster:

Brute Force & WAFEnable Brute Force Attack Protection and Web Application Firewall features for LiteSpeed.
Let’s EncryptInstall Let’s Encrypt SSL with Auto-Renewal to issue and renew a free SSL certificate.
WordPress MultisiteConfigure a WordPress Multisite Network.
Multi-region WordPress cluster installation
Configure topology, regions, scaling strategy, and advanced features.

Installation time varies according to the number of regions and selected options. When deployment finishes, the dashboard displays a success notification and an email is sent with the required access credentials.

For the best multi-region experience, assign a custom domain and configure DNS load balancing to distribute traffic between the regions.

Expected Result

A distributed WordPress deployment is created across multiple Virtuozzo Application Management regions. The standalone package links two WordPress Standalone environments, while the cluster package provides a multi-region WordPress Cluster with selectable asynchronous or Galera-based database distribution and Geo-Replicated GlusterFS storage.

Important Notes

  • Multi-Region WordPress Standalone requires exactly two selected regions during the documented installation workflow.
  • Its first environment is primary and the second is replica by default.
  • Async Primary-Replica Distribution requires at least two regions.
  • Sync Galera Distribution requires at least three regions.
  • The source recommends Sync Galera only when average ping between all regions is below 20 ms; otherwise use Async Primary-Replica.
  • GlusterFS Geo-Replication synchronizes static assets across regions.
  • Custom domains and DNS load balancing are recommended for geo-distributed traffic delivery.