All geek questions in one place

MySQL in AWS EC2 - How does it scale?

When you go beyond using one instance for your database, what are the best practices for using EC2? If the first instance is a master and you deploy the slaves, will they need to scan the transaction log and update them before the subordinates are correct? If the owner ran for a while and was busy, it can take a very long time, right? Is it wiser to use something other than master-slave on EC2? I saw that MySQL Enterprise supports EC2, but it was not clear to me (on me) on the MySQL site what features it added. Does it have some additional features that make new instances spawn quickly and on a turn-key basis?

Basically, I am trying to understand how you automatically scale a database.

+4
source share
1 answer

You can also use Amazon RDS (their version of MySQL is in the cloud) and completely refuse to work with the MySQL server (you will pay a little more for the server instance, but you can take database snapshots / etc.).

Amazon RDS currently supports five classes of database instances, starting at 11 cents per hour, up to 3.10 per hour:

* Small DB Instance: 1.7 GB memory, 1 ECU (1 virtual core with 1 ECU), 64-bit platform. * Large DB Instance: 7.5 GB memory, 4 ECUs (2 virtual cores with 2 ECUs each), 64-bit platform * Extra Large DB Instance: 15 GB of memory, 8 ECUs (4 virtual cores with 2 ECUs each), 64-bit platform * Double Extra Large DB Instance: 34 GB of memory, 13 ECUs (4 virtual cores with 3,25 ECUs each), 64-bit platform * Quadruple Extra Large DB Instance: 68 GB of memory, 26 ECUs (8 virtual cores with 3.25 ECUs each), 64-bit platform
+1
source

Source: https://habr.com/ru/post/1303689/

More articles:


All Articles