当你超越了使用一个实例，为你的数据库，使用EC2时，什么是最好的做法是什么？如果第一个实例是一个高手，你就旋转起来的奴隶，他们将需要扫描事务日志，并把自己最新的前奴隶是可用正确的？如果主已经运行一段时间，是繁忙的，这可能需要很长的时间，对吧？它是更聪明的使用，除了主从式的东西在EC2上？我已经看到了MySQL企业版具有EC2的支持，但目前还不清楚（我）在MySQL网站有什么特点这增加。它有一些附加的功能，使得产生新的实例，快速，交钥匙样？

When you move beyond using one instance for your database, what is the best practice when using EC2? If the first instance is a master and you're spinning up slaves, they would need to scan the transaction log and bring themselves up to date before the slaves are useable correct? If the master had been running awhile and was busy, this could take a very long time, right? Is it smarter to use something besides master-slave on EC2? I've seen MySQL Enterprise has support for EC2 but it wasn't clear (to me) on the MySQL site what features this adds. Does it have some added functionality that makes spawning new instances fast and turnkey-like?

从根本上说，我试图找出如何自动规模的数据库。

Fundamentally, I'm trying to figure how you auto-scale the database.

推荐答案

您也可以使用亚马逊RDS （其云计算的MySQL版本），并得到了运行的MySQL服务器业务的完全（你会付出稍多每个服务器实例，但你可以做数据库的快照/等）。

You could also use the Amazon RDS (their version of MySQL in the cloud) and get out of the running a MySQL server business altogether (you'll pay slightly more per server instance but you can do database snapshots/etc.).

亚马逊RDS目前支持五种数据库实例类，开始以每小时11美分一路去$ 3.10一小时：

Amazon RDS currently supports five DB Instance Classes, starting at 11 cents an hour going all the way to $3.10 an 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