Question

Require more details regarding Managed MySQL services

Posted October 23, 2019 373 views
DigitalOcean Managed MySQL Database
  1. How is read scaling performed? For example if an existing architecture utilizes one master and two slaves for reads, how does this translate into an equivalent digital ocean managed mysql package?

  2. Where are backup data stored? How do we access backups when necessary?

  3. Are standby nodes geographically dispersed or hosted in the same datacenter as the primary nodes?

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

2 answers

Hello, @whitwhoa

I will recommend you to check their official documentation as you can answer more of your questions by checking it:

https://www.digitalocean.com/docs/databases/mysql/
https://www.digitalocean.com/community/tutorials/understanding-managed-databases

Regarding the backups you can also use automation for backups so this can be really handy. You can check this tutorial on how to restore a MySQL cluster from Backups:

https://www.digitalocean.com/docs/databases/mysql/how-to/restore-from-backups/

I hope this helps!

by Mark Drake
Managed databases were developed to reduce the pain points commonly associated with database administration. This conceptual article outlines what managed databases are, how they can be beneficial to development teams, and some practical considerations one should make before building an application on top of one.

So I spun a few Managed databases (1/2/4 GB RAM) to run some tests in the context of Wordpress, and noticed that it is currently not possible for the user to tune MySQL performance by changing various cache sizes to fit the workload.

Support has kindly said that they could make some of these changes upon request but that would make the iteration cycles VERY SLOW if we have to go to them every time we want to try a new setting.

Ideally, we would be able to have access to key elements of the configurations either from the GUI, or from a command-line.

Even if I over-provision a relative large Managed DB (4GB RAM), things like innodbbufferpool_size seems to remain at 16MB by default, and not accessible for tweaking.

Finally, when running load tests, the current insights are a good start, but still very vague when compared to AWS RDS Insights.

Hope this can evolve soon, but without solid options to tune performance, we’re not ready to use it. Love the concept, but it needs a few more things.

Submit an Answer