Horizontal scaling with Project Mercury & EC2

We encourage users to post events happening in the community to the community events group on https://www.drupal.org.
jjaa's picture

I love Project Mercury, and I'm ready to use it in production, but I don't know how I'm going to scale it horizontally if it gets a ton of traffic. Some steps are obvious (use CloudFront for images), but I've read conflicting advice on other steps (striping two EBS volumes and using it for MySQL might be faster, but might cost a lot more for data transfer), and since my LAMP background is entirely self-taught some pieces are totally confusing for me. Can anyone give me good advice on a really scalable setup for Mercury on EC2?

Comments

Theres not much in the way of

Macronomicus's picture

Theres not much in the way of big data transfer costs with mysql on an array as its still the same amount of data either way.

The xfs raids have been unstable for me with the mercury AMIs, I did manage to get them working nicely on an ubuntu karmic test build I made, but not jaunty which mercury is built on.

As far as the scaling, take a look around the amazon docs for info on the load balancer service they offer, its relatively cheap and works with cloudwatch to deploy and terminate instances based on multiple scenarios. Im still researching it all and will test a bunch then probably hire someone to help get that aspect finalized when the time come.

Dont know if you saw it yet but here is the other group related to mercury
http://groups.drupal.org/pantheon