Architecture of MySQL on EBS for scaling (Amazon Web Services)

Question

I'm trying to understand how to architect an Amazon Web Services application.

I have an instance running off of EBS. As far as I understand, I need to mount the EBS drive so that I can store my MySQL database on it.

When I later want to scale up, how do I do so? I understand that I can add more server instances, but how will they be accessing the database? Since from what I understand, the EBS volume can only be attached to one server instance.

score 2 · Answer 1 · answered Dec 27 '10 at 14:13

I can't speak to this particular setup as I do not have experience using EBS with a MySQL instance but how this type of scaling is typically accomplished is by dedicating a particular instance as the master database server. Any time you spin up additional web servers those are still using the master DB IP to connect. At the time in which your database is the bottleneck you then spin up a slave DB instance on one of the boxes (or its own dedicated box). You can then configure replication in either a master to slave direction or a circular replication so that you can write to the slave instance as well.

If you choose the classic master to slave replication then you will have to make sure your writes are only performed on the master DB instance.

You can setup something like Zeus or any other connection load balancer so that you only ever have to connect to a single Database IP which will then round-robin route your read connections to your pool of servers. Otherwise you'd have to manage the connections yourself which is definitely not trivial. Good luck.

You might be able to load balance the MySQL slaves behind an 'ELB' in AWS... probably ideally one inside a VPC. — Christopher, Apr 16 '13 at 02:55

score 0 · Answer 2 · edited Apr 12 '13 at 20:06

0

EBS Volumes capacity can be scaled up using Snapshot->launch new volume technique, alternatively storage capacity can be scaled out using EBS Striping (RAID 0).

In AWS you cannot mount same EBS Volume to 2 EC2 instances simultaneously, so when you are scaling your application you need to scale out / up your MySQL DB either thru Replication or clustering. AWS RDS is a very good option for MySQL , if your application is read intensive then you can scale out using RDS Read replica's as well. If you need write scaling then functional partition or MySQL Shards can be explored.

edited Apr 12 '13 at 20:06

Andrew Barber

39,603
20
94
123

answered Apr 11 '13 at 15:20

Harish Ganesan

743
5
4

You can also crank IOPS into the EBS volumes to increase RW performance, but it's not at all cheap. – Christopher Apr 16 '13 at 02:53

score 0 · Answer 3 · answered Apr 15 '13 at 19:13

0

AWS has an entire product dedicated to this: RDS.

In all but the rarest and most specialized of circumstances you're going to be better off using RDS than trying to create and tune your own EBS/EC2/MySQL infrastructure.

RDS also directly answers your question - they directly enable the creation of readonly databases to use as query slaves. RDS also performs backups, upgrades, and all sorts of fail-over infrastructure for you.

With EBS there's no way to attach a disk to multiple EC2 instances, so you're not going to be able to build out a failure cluster using that approach. Instead you're going to need replication or backup tools of some type.

answered Apr 15 '13 at 19:13

Chris M.

1,731
14
15

`RDS` is absolutely a solution, but I take issue with a few of your points. RDS isn't the appropriate solution at this time if you need SUPER() privileges or if you're particularly cost-conscious. Also backing up EBS-backed mysql volumes is a breeze: Just snapshot them. It's doable with a single AWS API call and costs peanuts compared to a new disk in a physical server. EBS-backed dbs have their downsides, but `RDS` is not always the answer. – Christopher Apr 16 '13 at 02:51
@Christopher. I agree, the lack of SUPER privileges and the pricing can be a problem for some users. Personally, I find the automatic backups of RDS to be easier than snapshotting EBS volumes, although writing and scheduling a script to do this is easy enough. For general usage of MySQL, I have found RDS to be a good overall solution and less work than setting it up myself on EC2+EBS. – Chris M. Apr 18 '13 at 19:11

score 0 · Answer 4 · edited May 23 '17 at 11:55

0

Growing Amazon EBS Volume sizes

edited May 23 '17 at 11:55

Community

1
1

answered Feb 04 '11 at 02:43

Vic

1,336
11
30

score 0 · Answer 5 · edited May 23 '17 at 11:47

0

You can give a try to MySQL clustering on your EBS backed instances. I have similar query, with more requirements, posted here.

edited May 23 '17 at 11:47

Community

1
1

answered Aug 28 '11 at 08:15

vikas

1,535
1
13
22

Architecture of MySQL on EBS for scaling (Amazon Web Services)

5 Answers5