Databases Reference
In-Depth Information
Nevertheless, MySQL runs great in the cloud for lots of workloads. In general, you'll
be fine if you can fit your working set in memory, and if you don't generate a higher
write workload than your cloud-based I/O can handle. With careful design and archi-
tecture, and by choosing the correct version of MySQL and configuring it properly, you
can match your database's workload and capabilities to the cloud's strengths. Still,
MySQL isn't a cloud database by nature; that is, it can't really use all of the benefits
cloud computing theoretically offers, such as auto-scaling. Alternative technologies
such as Xeround are attempting to address these shortcomings.
We've talked a lot about the shortcomings of the cloud, which might give you the
impression that we're anti-cloud. We're not. It's just that we're trying to focus on
MySQL, instead of listing all of the benefits of cloud computing, which would not be
much different from anything you'd read elsewhere. We're trying to point out what's
different, and what you really need to know, about running MySQL in the cloud.
The biggest successes we've seen in the cloud have been when decisions are motivated
by business reasons. Even if the cost per business transaction is higher in the cloud over
the long term, other factors, such as increased flexibility, reduced upfront costs, re-
duced time to market, and reduced risk, can be more important. And the benefits to
the non-MySQL parts of your application could far outweigh any disadvantages you
experience with MySQL.
