Our Managed Database for MySQL offers a hassle-free, secure, and reliable database solution. Each instance comes with a pre-created database, supporting one database per instance, provisioned automatically at the time of creation. Ideal for developers and teams who want to focus on building applications without worrying about setup, maintenance, or patching. Read more
Locations
The product is present in the following locations:
- dc-fbg1 (our DC in Falkenberg, Sweden)
- dc-sto1 (our DC in Stockholm, Sweden)
- dc-oul1 (our DC in Oulu, Finland)
Technical Specification
| Customer self-service | Yes. Managed in Glesys Cloud and available via API |
| Engine version(s) | MySQL version 8.0 |
| Disk IOPS | 12,000 |
| Supported storage engine(s) | InnoDB |
| Primary key constraint | Yes |
| Database replication feature | No |
| Automated failover feature | No |
| Change engine version support | No |
| Root user privileges | No |
| User-specific database permissions | No |
| Encryption at Rest | No |
| Encryption in Transit | Yes (uses the TLS protocol) |
| Availability and access | By default, all traffic is blocked. As a user, you add IP addresses that are allowed to connect to the database. |
| Disk full failure prevention | Database instances automatically switch to read-only mode when the disk is almost full, with 3 GiB remaining. Preventing writes stops the disk from continuing to fill and keeps the instances available for reads. During the read-only mode, you can take measures to free more disk space. |
| Processing of personal data | Storage, transfer |
Automated backup
| Backup plan | One daily backup with 14-days retention |
| Custom schemes | No |
| Remote backups | Yes |
| Point-in-time recovery (PITR) | No |
Predefined plans
Glesys offers a wide spectrum of plans to serve use cases that range in size from personal blogs to large datasets and high-transaction applications.
Please note that there is currently no feature in the UI to switch plans. However, users can utilize a SQL dump provided by us and restore it to a new instance with the desired resources.
| vCPUs | Memory | Storage | Max. Connections |
|---|---|---|---|
| 1 | 4 GiB RAM | 25 GiB | 400 |
| 1 | 4 GiB RAM | 50 GiB | 400 |
| 2 | 8 GiB RAM | 50 GiB | 800 |
| 2 | 8 GiB RAM | 100 GiB | 800 |
| 4 | 16 GiB RAM | 50 GiB | 1,600 |
| 4 | 16 GiB RAM | 100 GiB | 1,600 |
| 4 | 32 GiB RAM | 150 GiB | 3,200 |
| 4 | 32 GiB RAM | 300 GiB | 3,200 |
| 8 | 64 GiB RAM | 150 GiB | 6,400 |
| 8 | 64 GiB RAM | 300 GiB | 6,400 |
| 8 | 128 GiB RAM | 150 GiB | 12,800 |
| 8 | 128 GiB RAM | 300 GiB | 12,800 |
Monitoring
Monitoring is available via a Prometheus-compatible endpoint; however, customers must set up their own solution to store historical metrics. Access to systemd logs and the slow query log is not available.
Maintenance
You will be assigned a regular and recurring day and time each week for maintenance. Occasionally, Glesys performs maintenance tasks on the managed MySQL database. These tasks typically include updating the underlying infrastructure of the database, such as patching the operating system, updating necessary libraries, or upgrading MySQL itself. Glesys manages these maintenance tasks automatically. During maintenance, the database may experience a brief period of downtime, which can last up to 10 minutes.
Responsibilities
| Infrastructure platform | Glesys |
| Database administration | Customer |
| SQL troubleshooting | Customer |
| MySQL performance troubleshooting | Customer |
| Automated backups | Glesys |
| Backup verification | Customer |
| Backup recovery* | Customer |