MySQL Multi-Region Cluster Hosting on MassiveGRID PaaS
The MySQL/MariaDB/Percona Multi-Region Cluster deploys database nodes in two or more MassiveGRID regions and links them with replication, so your data survives a whole-region outage and reads are served close to your users. Each region gets its own ProxySQL endpoint, and the installer handles the cross-region configuration.
MySQL Multi-Region Cluster on MassiveGRID PaaS installs in one click in New York, London, Frankfurt or Singapore, costs about $49.20 a month for the Starter configuration, 2 × Database node per region (1 GiB each) and 2 × ProxySQL per region (256 MiB each), and starts with a 14-day free trial. See the sizing table.
Both buttons open the MassiveGRID PaaS dashboard with MySQL Multi-Region Cluster pre-selected. Sign up without a card, name the environment, pick a region, and the package installs in a few minutes.
MySQL Multi-Region Cluster Package Facts
| Attribute | Value |
|---|---|
| Package | MySQL/MariaDB/Percona Multi-Region Cluster |
| Type | Application (installs a complete environment) |
| Category | Databases |
| Software vendor / project | Oracle (MySQL), MariaDB Foundation, Percona |
| Licence | GPLv2 (MySQL Community, MariaDB, Percona Server) |
| Runtime / stack | MySQL, MariaDB or Percona nodes distributed across MassiveGRID regions, ProxySQL per region |
| Regions | New York, London, Frankfurt, Singapore |
| Billing | Pay-per-use, about $49.20/month for the Starter configuration (20 cloudlets at $0.003372 per cloudlet-hour), no licence fee |
| Free trial | 14 days, no credit card |
| Uptime SLA | 100% |
What is MySQL Multi-Region Cluster?
A cluster inside one region protects against node failures. It does not protect against a regional network incident, a data-centre event, or the latency that users on another continent see on every query. This package addresses both by distributing a MySQL-compatible cluster across New York, London, Frankfurt and Singapore in any combination you choose.
Depending on the engine and mode selected, the regions are joined by asynchronous replication (suitable for a primary region with read replicas elsewhere) or by Galera-style synchronous replication (see the MariaDB Multi-Region Galera Cluster for that dedicated package). Applications in each region connect to their local ProxySQL, which routes writes to the correct primary and serves reads locally.
What the MySQL Multi-Region Cluster Package Deploys
Marketplace packages are not bare container images. One click provisions a complete, production-shaped environment on MassiveGRID infrastructure. How these nodes are sized and what they cost.
- Database nodes in each region: MySQL, MariaDB or Percona containers deployed to every region you select, each region holding a complete copy of the data.
- Cross-region replication: Replication channels between regions configured by the installer, with GTIDs so failover and re-pointing are safe.
- ProxySQL per region: A local entry point in each region that routes reads locally and writes to the primary.
- Regional environments: Each region's nodes live in their own environment, so they can be scaled and monitored independently.
What MySQL Multi-Region Cluster Costs to Run
Three starting configurations for the MySQL Multi-Region Cluster package, sized in cloudlets (1 cloudlet = 128 MiB RAM + 400 MHz CPU) and priced at the published rate of $0.003372 per cloudlet-hour, or $2.46 per cloudlet-month.
| Configuration | Topology | Cloudlets | Est. per month |
|---|---|---|---|
| StarterTwo regions | 2 × Database node per region (8 cloudlets, 1 GiB each), 2 × ProxySQL per region (2 cloudlets, 256 MiB each) | 20 | $49.20 |
| StandardThree regions | 3 × Database node per region (16 cloudlets, 2 GiB each), 3 × ProxySQL per region (2 cloudlets, 256 MiB each) | 54 | $132.84 |
| ProductionThree regions, large datasets | 3 × Database node per region (32 cloudlets, 4 GiB each), 3 × ProxySQL per region (4 cloudlets, 512 MiB each) | 108 | $265.68 |
Estimates assume the environment averages the listed cloudlets around the clock; billing is hourly, vertical auto-scaling lowers the figure when the application is idle, and volume discounts apply as usage grows. Disk and external traffic are billed per gigabyte on top. No licence fee applies to the package. Pick a row in the installer by setting the cloudlet limits per node, or start small and let auto-scaling grow it. Price a different topology or a working-hours schedule in the PaaS pricing calculator; the PaaS page describes the billing model.
Why Teams Choose MySQL Multi-Region Cluster
Survive a region loss
A full copy of the data in every selected region means an outage in one location does not lose data or availability.
Local reads worldwide
Applications read from the replica in their own region, cutting query latency for global user bases.
Data residency options
Choose exactly which regions hold data, for example Frankfurt and London for an EU-only footprint.
Managed cross-region setup
Replication users, GTIDs and proxies are configured for you; cross-region MySQL by hand is a multi-day task.
How to Install MySQL Multi-Region Cluster on MassiveGRID PaaS
Installing the package takes three steps and a few minutes of waiting. No servers to provision, no configuration files to edit.
Open the installer
Click Install with free trial or Install to my account. The MassiveGRID PaaS dashboard opens with the MySQL Multi-Region Cluster package pre-selected, so nothing has to be copied or pasted.
Sign up or sign in
New to the platform? Sign up for the free 14-day trial, which needs no credit card. Existing customers sign in with their usual dashboard credentials.
Choose region and deploy
Name the environment, pick New York, London, Frankfurt or Singapore, and confirm. The platform builds every MySQL Multi-Region Cluster node, wires them together and hands you the live URL and credentials.
Who Runs MySQL Multi-Region Cluster on PaaS
Global SaaS back ends
Applications with users in the Americas, Europe and Asia that need low read latency everywhere.
Disaster-recovery databases
Companies whose continuity plan requires a live replica in another jurisdiction with minimal replication lag.
Multi-region web clusters
The database layer for the Multi-Region WordPress Cluster and similar geo-distributed applications.
Why Run MySQL Multi-Region Cluster on MassiveGRID PaaS
Built for uptime. MySQL Multi-Region Cluster runs on MassiveGRID's high-availability platform, where every environment is covered by a 100% uptime SLA. Nodes live on redundant hosts, storage is replicated, and failed containers are restarted or migrated automatically.
Pay for what you use. Billing is hourly and per cloudlet (128 MiB RAM plus 400 MHz CPU). Vertical auto-scaling adds and removes cloudlets as load changes, so a quiet MySQL Multi-Region Cluster environment costs a few dollars a month and a busy one grows without a migration. Full details are on the PaaS page.
Your choice of jurisdiction. Deploy in New York, London, Frankfurt or Singapore and keep data inside the region your users or regulators require. MassiveGRID is ISO 27001 and ISO 9001 certified and GDPR compliant, and has run hosting infrastructure since 2003.
No lock-in. The package is a standard Jelastic Packaging Standard (JPS) manifest. You keep root-level access to the containers, can export the manifest, and can move the workload to any other Jelastic-compatible platform or to your own servers at any time.
Related on massivegrid.com: Data Centres · Disaster Recovery.
MySQL Multi-Region Cluster Questions
MySQL Multi-Region Cluster Guides from the MassiveGRID Blog
Scenario-driven guides on running MySQL Multi-Region Cluster on MassiveGRID PaaS, written for the developers, operators and buyers who deploy it. Browse the blog.
More from the Marketplace
Packages that are often deployed alongside MySQL Multi-Region Cluster, or that solve the same problem a different way. Browse all 83 packages.
Deploy MySQL Multi-Region Cluster Today
Start the free 14-day trial and have MySQL Multi-Region Cluster running in minutes. No credit card required.