|By Don MacVittie||
|May 10, 2010 02:45 PM EDT||
The ongoing saga of everything cloud is entertaining, if nothing else. I have a couple of areas of interest that aren’t really burning up the electrons, one of them is cloud databases. Let’s face it, while “the cloud” is interesting in an application sense, for IT it is relatively useless without the ability to access databases. Normally databases housed in your internal IT department. Of course internal “private” clouds will address much of this issue, until they are readily available, we are faced with the reality that we have to find a solution we can trust to house data that is essential to our organization’s well being. There are a lot of issues around data in the cloud, I’m going to focus in on a couple that IT departments are trying to figure out – or should be.
- Security – data access control and standards compliance
- Security – physical/network control
- Latency – how much impact will remote databases have on performance
- Standards – how is data put into and gotten out of the database
- Data Redemption – how do I get my data out if for any reason we stop doing business?
There’s a lot there, but it’s not nearly as long as the list could be if I was to dissect all of the services out there. For the record, any “cloud data solution” that includes the phrase “frees you from the restrictions of an RDBMS” or “develop applications without IT” are not considered here. My reasoning is simple, your organization holds a ton of critical and relevant data in RDBMS databases now, changing that is possible, but at least for the time being, these applications will be limited to business units or pretty small businesses. I am looking at the problem from the IT perspective. No doubt I missed some vendors – Cloud is the winner of 2010’s buzzword bingo after all, and I was just researching with my own resources.
And a final note, I have not gone and tried any of these databases. There just isn’t time to do that level of research for a blog post. So understand that I am working off of the web pages of these vendors. Still, the market is young enough that for many, you can tell what they’re about pretty reliably.
Of all of the products that I explored, I have to say that Caspio Bridge has done the most to resolve the security and standards issues. They are PCI and TRUSTe compliant, which speaks volumes. They offer SQL Server with an AJAX front end, and allow you to get the data out in a selection of formats that includes XML and CSV, which is “good enough” for the current state of cloud databases, I would think.
Then there is Dabble DB who has a disclaimer about HIPPA that is understandable and probably helps the lawyers sleep at night, but isn’t designed to win customers’ confidence:
- Does Dabble DB® comply with HIPAA?
Both Microsoft’s SQL Azure and Oracle via AWS are solid DB offerings but offer little tangible in terms of security. They are very desirable in the sense that they offer their standard interfaces, making it pretty easy to adapt your applications to them, but both are relatively silent about security other than the role-based security built into their RDBMS, which is a bit disconcerting. Rackspace and Joyent both offer complete cloud solutions, and honestly these two providers do the best job of documenting what is available and how to use it. But again, they seem to miss the point that users care about the level of their security. Now granted, with so much documentation on their sites, I’m guessing there is more info there than I found about the security issues.
Truly, Oracle, Azure, and Rackspace are the ones you have the least to worry about where latency is concerned – these companies (actually Amazon in the case of Oracle) have huge, dispersed datacenters, and data redemption is pretty straight-forward from all four of the vendors mentioned in the last paragraph, simply because they use the databases we all use. Disclosure: We are partners with Oracle and Microsoft, but I assure you that their inclusion is based upon the fact that you have one or both running in your datacenter already, not because of our partnership.
Well, you might be asking what the point of this blog is… And honestly I have had an interest in this topic for a while, but only now got the time to start research. I went into this thinking I would be sorely disappointed because no one was talking about the database where cloud is concerned. There are still serious issues – if you fall under HIPPA, can you put your data on someone else’s network? How about PCI? Do your execs believe that this other company will be as cautious with your data as your employees? What is the recourse if one of those other apps in the cloud gets into your space? Don’t ever let a cloud provider tell you it can’t happen. It can, they’re on the same network, often on the same physical hardware. But overall? I wasn’t at all disappointed. Not a bit.
You see, I expected to find the state of cloud databases to be much, much more sparse and juvenile than what I found. Lots more juvenile than what I found.
I’m not yet certain what I think of treating your cloud database as ‘just another app’, since it holds sensitive information and a cloud is not your private network. Remember: for a few bucks a month a hacker can legally be on the same physical network as your DB, something we’ve spent years and a small fortune preventing. But if you trust your IT staff’s (or your own if you are IT staff) ability to lock down MySQL or SQL Server or Oracle like it was on a public IP address, then this is probably a good choice for you.
Caspio really did do the best job of convincing me that they’re on to the security stance though. Seriously, they didn’t bury their claims in legalese or tons of other disclaimers and documentation, they listed their certifications and what precautions they take with both physical access and staff access to your data. Still leaves the question of how well they can detect suspicious activity coming from a “customer” instance, but since they’re selling DB services and not OS instances, this is a little less of a concern (though certainly don’t dismiss the risks, AJAX can be an attack vector also).
I want to look at this from the other side that IT cares about – which app or server vendors have a method for you to securely link back to your own database. You could always write a proxy to handle access or lock your server down to only accept requests from a specific IP range, but I want to understand how that lockdown would impact scale-up and if it was loose enough not to impact scale-up, what that would mean to other “customers” who paid their few bucks a month. I’ll explore that topic in a future blog though, for Monday’s blog is already upon me.
But for now, it’s late, and I’ve (hopefully) given you something to think about at least, and given myself a ton to think about.
- Cloud Database – Are You Prepared?
- The Storage Future Is Cloudy, and It's About Time
- Making Android SSL Work Correctly
- Oracle Enterprise Manager Grid Control Plug-in for BIG-IP LTM Beta
- CIOs Should Know that IT Is Infrastructure as a Service
- A Rose by Any Other Name - Appliances Are More Than Systems
- So You Think You're Enterprise Class?
- Minnesota and Private Cloud
- v.10 - iSessions in the Cloud (or a remote data center, you choose)
- Like “API” Is “Storage Tier” Redefining Itself?