I've been writing a bit recently about virtualization, specifically how database virtualization works. And in my quest to get up to speed on this new topic, I've been poking around a number of blogs that cover virtualization. Today I came across InfoWorld's Virtualization Report, where David Marshall ran down IDC's predictions for what's next in virtualization. You can listen here.
I find the predictions perfectly reasonable, but it was what I didn't hear that got me to thinking. No one is talking about virtualizing databases. Granted, I have an agenda (find me a blogger who doesn't). I'm already convinced database virtualization is the next big thing. So let me try and lay out a way of thinking about this from a customer perspective.
The main driver of virtualization is cost reduction, right? So vendors and IT shops have attacked the very expensive areas of servers and storage. Makes sense. So what's another commoditized area that companies spend tons of money on, and that keeps getting bigger and harder to maintain every year? Answer: Databases.
So I wonder why more attention is not being focused on this area. Perhaps we vendors have not done a good job explaining it. Database virtualization reduces the cost of maintaining dozens of custom data marts, allows movement of older databases to commodity hardware (or retirement altogether), and reduces the costly and time-consuming process of copying data.
In addition, database virtualization provides more flexibility in deployment (another oft-touted benefit of virtualization) and rapid response to change (yet another).
For the database guys who claim that databases are a horse of a different color, too complex to be messed with, I ask you: What's the hottest trend these days in the database world? Master data management, right? Providing a virtual layer to control schemas for things like customer, partner, account, etc. seems just the ticket. And for those who say it will never be fast enough, we know that's just not true. First, not every database needs to be a screamer. And for the hot data (see my previous post on the temperature of data), just cache it.
So think about it. I'll bet you $100 that 100 out of 100 CIOs would love to reduce the number of databases in their organizations.
What's next for virtualization? I say databases. Just follow the money.