Ask any MySQL Database Administrator or database-savvy Developer how smooth their last MySQL master/slave swap went, and unless they live in a perfect world, they likely encountered a hiccup or two. The actual reconfiguration of replication probably went well, as "CHANGE MASTER TO" is hard to mess up if you're being careful. But controlling application behavior isn't always easy...
One of the hottest topics in computing today, by way of fast innovation and controversy, is whether or not to rely on the public cloud. Lured by the convenience and cost-effectiveness of these services, some computer users and business owners put their applications and data into the cloud without a moment's hesitation.
Over the past two years, I've had the opportunity to work with Rackspace Cloud on multiple levels and from multiple directions. I've been quite impressed with the technology, the team's knowledge and willingness to help customers, the advancement of features, and the growing community.
We're currently beginning a project that clones an environment currently setup at Amazon EC2 to Rackspace Cloud. Both environments will operate mostly independently, but still need to be implemented in a similar fashion. Without getting into too many details, I decided to make a quick blog post to compare the pros/cons of Amazon EC2 vs. Rackspace Cloud.
We've been working on a project using Amazon Web Services for the past few years. One of the main concerns I have is the inability to change a server from one security group to another once deployed. I'm sure there are very good reasons for security groups being designed this way (the setup is most likely iptables on the host node behind the scenes), but when trying to long-term EC2 instances, it's a System Engineer's worst nightmare to not have full control over firewall configuration.