If you thought running a database in the cloud was easy, think again. Databases in a cloud environment are inherently different from traditional installations in a datacenter or even in your trusted hosted environment.
There are four key considerations we believe every system architect should take into account when designing their database for the cloud. Today I’ll explain each of them, and why achieving those requirements in a cloud environment might be more complex, tedious and expensive than you think.
Here’s what you’ll need:
Today’s session will also review various potential database solutions. We’ve discovered that the best solution seems to be a SQL database with NoSQL capabilities. Amazon RDS is an example of a preconfigured MySQL DBaaS that targets developers and admins who are likely to shy away from manually configuring and running MySQL in the cloud. Other vendors offer alternate storage engines underneath and/or application sharing/middleware on top. In this session we will discuss these approaches and others that try to satisfy both ends of the spectrum such as scalable, hybrid DHT (distributed hash tables) and hybrid SQL/NoSQL solutions.
Eran Levin, VP R&D, is an experienced technical executive, with more than 20 years of managing both development and product groups throughout the design cycle, from concept to release.(http://il.linkedin.com/in/eranlevin)
For information on exhibition and sponsorship opportunities at the conference, contact Yvonne Romaine at firstname.lastname@example.org
For media partnerships, contact mediapartners@ oreilly.com
For media-related inquiries, contact Maureen Jennings at email@example.com
To stay abreast of conference news and to receive email notification when registration opens, please sign up for the O'Reilly MySQL Conference Bulletin (login required).
View a complete list of O'Reilly MySQL Conference Contacts