The fundamentals of the Managed MariaDB offering
The service Managed MariaDB is a fully managed MariaDB open-source relational database deployed on Cloud Temple's sovereign SecNumCloud infrastructure. Based on MariaDB Community Server (LTS version) and a Galera Cluster for production, this service guarantees synchronous multi-AZ high availability with automatic failover and no loss of data.
Designed for both mission-critical transactional applications and analytical workloads, this service handles all the operational complexity of a database cluster: deployment, replication, backups, point-in-time recovery (PITR), updates and monitoring. Application teams can concentrate on their data, not their infrastructure.
Our compliance procedures
Our Managed MariaDB offering is HDS and ISO 27001 certified, and available on SecNumCloud qualified and C5 compliant services.
The benefits of Cloud Temple's Managed MariaDB offering
Your data, never lost
RPO = 0 guaranteed in production
Ensure maximum protection with Galera synchronous replication: no validated transaction can be lost, even in the event of a complete datacenter failure.
An always-available base
Automatic changeover without interruption
Maintain service continuity with native failover: in the event of failure, the remaining nodes continue to serve requests without user impact.
Restore to the second
PITR and continuous backups
Go back precisely before an incident thanks to a combination of full backups and binary logs, for total control of your data.
Focus on your applications
An operated, MySQL-compatible 100% database
Delegate complete operation (replication, updates, monitoring) while maintaining total compatibility with your existing tools and applications.
Key features of the Managed MariaDB offering
Galera Cluster (synchronous HA)
Synchronous cluster on 3 nodes (1 Primary, 2 Secondary). wsrep (Write-Set Replication): each transaction is certified and validated by all nodes before confirmation. RPO = 0, automatic failover.
MaxScale (Proxy & Router)
High-availability MariaDB proxy (active/active x2) providing read/write splitting, connection pooling, automatic detection of failed nodes and load balancing of read requests.
Point-in-Time Recovery (PITR)
Restore the database at any time. Uses full physical backups (mariabackup) and continuous archiving of binary logs on Object Storage S3.
Automatic (physical) back-ups
Full physical backups (volume snapshots) scheduled (daily/weekly) via mariabackup (hot backup without service interruption) stored on Object Storage Cloud Temple, encrypted at rest.
Logical backups (optional)
Scheduled logical backups (mysqldump), offering database-level granularity for restores and exports. Stored on Object Storage Cloud Temple.
TLS 1.3 encryption
Encryption of all Galera client-server and inter-node connections (wsrep) using TLS 1.3. X.509 certificates managed by Cloud Temple.
Encryption at rest
Transparent encryption of data (InnoDB tablespaces) and backups in AES-256.
Authentication & Authorisation
Native management of MariaDB user accounts with ed25519 (recommended), sha256_password or mysql_native_password authentication. Optional LDAP/PAM integration. Granular permissions by database, table and column.
InnoDB engine (default)
Default ACID transactional storage. Support for foreign keys, transactions, MVCC (Multi-Version Concurrency Control). Fully compatible with MySQL InnoDB.
Slow Query Log
Configurable slow query log activation with configurable threshold. Export to centralised client logs for analysis and optimisation.
Customisable configuration
Key MariaDB parameters configurable according to application profile (innodb_buffer_pool_size, max_connections, character_set, timezone, sort_buffer_size, tmp_table_size) via change management request.
Insulation by dedicated instance
Each customer has their own MariaDB cluster on a dedicated infrastructure, with an isolated private network. No sharing of data between customers.
Technical specifications
Do you have a database migration project or a critical high-availability requirement? Let's talk.
Whether you're looking to modernise a legacy application (Lift & Shift MySQL/MariaDB), guarantee zero data loss (RPO=0) with a Galera multi-AZ cluster, or any other project, our experts will work with you. We'll help you size your instances, define your backup rules (Point-in-Time Recovery) and configure your network isolation.
Share the details of your project with us using this form: we'll get back to you quickly to design the database architecture that's right for your performance and compliance needs.
Use cases
No, the network is totally isolated.
Access to your MariaDB instances (or to your MaxScale proxy) is exclusively possible from your private Cloud Temple network (via IPsec VPN or dedicated interconnection). No MySQL endpoint is exposed on the Internet, which considerably reduces your attack surface and meets compliance requirements (PCI-DSS, HDS, LPM).
To guarantee an RPO (Maximum Data Loss) of zero.
Unlike traditional asynchronous replication (Primary-Replica), which tolerates a replication delay and a risk of data loss in the event of a failover, our production architecture is based on synchronous wsrep replication across 3 datacentres (multi-AZ). Each transaction is certified and validated by all the nodes before being confirmed to the customer. If a datacenter goes down, your validated data is intact and the switchover takes place automatically in less than 30 seconds.
No, routing is totally transparent.
In production, the MariaDB cluster is preceded by the MaxScale high-availability proxy. It automatically performs read/write splitting: it directs writes to the primary node and distributes your read requests (load balancing) to the secondary nodes. Your applications (PHP, Java, Node.js, etc.) connect normally, with no refactoring required.
A restoration possible down to the second.
Cloud Temple automates full physical “hot” backups (via mariabackup) without service interruption, stored on an encrypted S3 Object Storage. This backup, combined with continuous archiving of your binary logs, enables Point-in-Time Recovery (PITR): you can go back in time to the last validated transaction before an incident. The standard retention period is 7 days, extendable to 30 days as an option.
Reversibility is native and there is no proprietary locking.
Under the Data Act, your data belongs to you. You can export it at any time in self-service via standard SQL dumps (mysqldump), recover a physical snapshot (mariabackup) free of charge within 15 days, or even extract your data in real time via Change Data Capture (CDC / Debezium). If you cancel, your databases, backups and binary logs will be securely purged within 7 days.