MariaDB Master-Master Replication on MassiveGRID PaaS
The MariaDB Master-Master Replication package deploys two MariaDB nodes that replicate to each other, so both accept writes and each holds a complete, current copy of the data. It is a light-weight way to add redundancy and read capacity to a MariaDB database without the coordination overhead of Galera.
MariaDB Master-Master Replication on MassiveGRID PaaS installs in one click in New York, London, Frankfurt or Singapore, costs about $39.36 a month for the Starter configuration, 2 × MariaDB node (1 GiB each), and starts with a 14-day free trial. See the sizing table.
Both buttons open the MassiveGRID PaaS dashboard with MariaDB Master-Master Replication pre-selected. Sign up without a card, name the environment, pick a region, and the package installs in a few minutes.
MariaDB Master-Master Replication Package Facts
| Attribute | Value |
|---|---|
| Package | MariaDB master-master Database Replication |
| Type | Application (installs a complete environment) |
| Category | Databases |
| Software vendor / project | MariaDB Foundation |
| Licence | GPLv2 (MariaDB Server) |
| Runtime / stack | Two MariaDB nodes with bidirectional asynchronous replication |
| Regions | New York, London, Frankfurt, Singapore |
| Billing | Pay-per-use, about $39.36/month for the Starter configuration (16 cloudlets at $0.003372 per cloudlet-hour), no licence fee |
| Free trial | 14 days, no credit card |
| Uptime SLA | 100% |
What is MariaDB Master-Master Replication?
Master-master (also called primary-primary or bidirectional) replication configures two MariaDB servers so that each one is a replica of the other. Writes on either node flow to the other asynchronously. It is a long-standing pattern for improving availability, sharing read and write load, and keeping a hot standby that can take over instantly if a node fails.
The package sets up the replication users, server IDs, auto-increment offsets and GTID configuration that make the pattern safe, which are the details that cause data collisions when done by hand. It suits applications that mostly write to one node and use the second for failover and reads, or that can partition writes so the two nodes never update the same rows concurrently.
What the MariaDB Master-Master Replication 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.
- Two MariaDB nodes: Independent containers, each configured as primary and replica of the other, with auto-increment settings staggered to avoid key collisions.
- Bidirectional replication: GTID-based asynchronous replication in both directions, configured and verified by the installer.
- Administrative access: Credentials and connection details for both nodes delivered to your dashboard and email.
- Optional encryption: Add the MySQL SSL/TLS add-on to enforce encrypted client connections.
What MariaDB Master-Master Replication Costs to Run
Three starting configurations for the MariaDB Master-Master Replication 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 |
|---|---|---|---|
| StarterDevelopment and small applications | 2 × MariaDB node (8 cloudlets, 1 GiB each) | 16 | $39.36 |
| StandardProduction databases | 2 × MariaDB node (16 cloudlets, 2 GiB each) | 32 | $78.72 |
| ProductionLarge datasets | 2 × MariaDB node (32 cloudlets, 4 GiB each) | 64 | $157.44 |
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 MariaDB Master-Master Replication
Instant hot standby
If one node fails, the other already holds all committed data and continues serving reads and writes.
Simple and low-overhead
No quorum, no certification: asynchronous replication keeps write latency unchanged.
Read scaling
Direct reporting or read-heavy traffic to the second node while the first handles writes.
Backup friendly
Take consistent backups from one node with the Database Backup/Restore add-on without pausing production.
How to Install MariaDB Master-Master Replication 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 MariaDB Master-Master Replication 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 MariaDB Master-Master Replication node, wires them together and hands you the live URL and credentials.
Who Runs MariaDB Master-Master Replication on PaaS
Small production applications
Web applications that want redundancy without a three-node cluster's cost.
Backup and reporting replica
Keeping a second node for dumps and heavy reports while production writes to the first.
Two-site active-passive setups
A standby that is always writable so failover requires only a connection-string change.
Why Run MariaDB Master-Master Replication on MassiveGRID PaaS
Built for uptime. MariaDB Master-Master Replication 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 MariaDB Master-Master Replication 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: Platform as a Service.
MariaDB Master-Master Replication Questions
MariaDB Master-Master Replication Guides from the MassiveGRID Blog
Scenario-driven guides on running MariaDB Master-Master Replication 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 MariaDB Master-Master Replication, or that solve the same problem a different way. Browse all 83 packages.
Deploy MariaDB Master-Master Replication Today
Start the free 14-day trial and have MariaDB Master-Master Replication running in minutes. No credit card required.