MySQL Cluster on MassiveGRID PaaS
The MySQL/MariaDB/Percona Cluster package deploys a replicated database cluster on MassiveGRID PaaS in one click. Choose the engine (MySQL, MariaDB or Percona) and the topology (primary-secondary, primary-primary, Galera, Percona XtraDB or MySQL InnoDB Cluster), and the installer configures replication, node auto-discovery and a ProxySQL entry point for you.
Both buttons open the MassiveGRID PaaS dashboard with MySQL Cluster pre-selected. The trial needs no credit card.
MySQL Cluster Package Facts
| Attribute | Value |
|---|---|
| Package | MySQL/MariaDB/Percona 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 database nodes with ProxySQL entry point |
| Regions | New York, London, Frankfurt, Singapore |
| Billing | Pay-per-use from $2.46/month ($0.003372/hour), no licence fee |
| Free trial | 14 days, no credit card |
| Uptime SLA | 100% |
What is MySQL Cluster?
Setting up database replication by hand is error-prone: server IDs, binary logs, replication users, GTIDs, quorum settings and a load-balancing proxy all have to agree. This package encodes the vendors' recommended configurations for each topology, so a highly available MySQL-compatible cluster is a form rather than a project. New nodes added by scaling are discovered and joined automatically.
The package serves as the database layer for many other marketplace packages, including the WordPress and Magento clusters, and can be attached to any environment. ProxySQL sits in front, routing writes to the appropriate primary and spreading reads, so applications connect to one endpoint and never need to know which node is which.
What the MySQL Cluster Package Deploys
Marketplace packages are not bare container images. One click provisions a complete, production-shaped environment on MassiveGRID infrastructure.
- Database nodes: Two or more MySQL, MariaDB or Percona Server containers with replication configured for the chosen topology.
- ProxySQL: A ProxySQL node providing a single connection endpoint with read/write splitting, health checks and automatic failover routing.
- Replication and auto-discovery: Replication users, GTID settings and cluster membership handled by the package, including for nodes added later by horizontal scaling.
- Orchestrator (where applicable): For asynchronous topologies, an orchestration component monitors replication health and promotes a new primary when needed.
- Management access: Credentials delivered to your email and dashboard, with phpMyAdmin-style management available from the platform.
Why Teams Choose MySQL Cluster
Five topologies, one installer
Primary-secondary, primary-primary, MariaDB Galera, Percona XtraDB Cluster and MySQL InnoDB Cluster (Group Replication), each pre-configured.
Single endpoint via ProxySQL
Applications connect to ProxySQL, which routes queries and hides failovers, so no connection-string changes during incidents.
Scale reads horizontally
Add replica nodes from the dashboard; the package joins them to the cluster and ProxySQL starts routing reads to them.
Encrypted connections optional
The MySQL SSL/TLS add-on enforces encrypted client connections across the whole cluster.
How to Install MySQL 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 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 Cluster node, wires them together and hands you the live URL and credentials.
Who Runs MySQL Cluster on PaaS
Database tier for web applications
WordPress, Magento, Laravel, Django and Java applications that need the database to survive a node failure.
Read-heavy analytics and reporting
Workloads that benefit from spreading reads across several replicas behind ProxySQL.
Migration from a single database server
Teams moving a monolithic MySQL to a replicated setup without re-architecting the application.
Why Run MySQL Cluster on MassiveGRID PaaS
Built for uptime. MySQL 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 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 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: Platform as a Service · High Availability.
MySQL Cluster Questions
More from the Marketplace
Packages that are often deployed alongside MySQL Cluster, or that solve the same problem a different way. Browse all 84 packages.
Deploy MySQL Cluster Today
Start the free 14-day trial and have MySQL Cluster running in minutes. No credit card required.