« Excited for the CloudStack Collab Conference EU | Main | My next career move »

The hidden value in CumuLogic DBaaS – Reducing Operational Risk by Making Availability Configuration Automatic

Fair warning - this is a commercial post origionally published on the CumuLogic corporate blog. That being said, I think that CumuLogic's DBaaS is valuable enough to share here on my personal blog as well.

As I spend the time to get to know the CumuLogic platform better in my new role, I’ve realized something that I think is worth sharing:

Not only are the modular / composable services useful as a developer or system administrator to make their application deployments easy, but deploying through CumuLogic platform is actually a great way to reduce your operational risk.

Think about it this way: If you’re a developer, how many times have you put off setting up a backup job for your new MySQL DB until it’s too late? For me, this is one of those tasks that I frequently forget to deal with. If you’re a sysadmin, what level of availability do you usually setup for your new databases? Do you settle for two nodes? Do you even get around to dual nodes if the requestor doesn’t ask for it? How about software updates? Do you always get to them on schedule?

The fact is, many, many databases are deployed without all of the appropriate configuration that makes them “production ready”. Backups, replicas and software updates all become trivially easy using CumuLogic’s DBaaS product. Seriously… it’s very easy.

Want your MySQL database to be in a three node cluster? Just pick that option. Want it to be 5 nodes? Click + on the node count field twice and, boom, done. Backups? No problem either… just a few clicks away, and you’ve picked a backup window, set a retention policy, and can feel confident that you’re data is safe.

An argument could be made that you could just use Puppet or Chef recipes to deploy your MySQL DB, and manage the configuration through that. Well, consider CumuLogic DBaaS as another tool in your toolbox that makes things even easier than before. How about combining your existing Puppet or Chef code with a call to the CumuLogic API to provision the database? Easily done.

Want to learn more? Head over to cumulogic.com.