“In every case in which a CIO or other executive has driven or authorized substantial investments in service-based database infrastructure, changes in DBA roles have followed. As two financial industry executives put it at a conference in Jersey City and re:Invent, respectively, their DBAs are all being moved to doing more generic DevOps-style roles, roles that involve more architecture and engineering than traditional database administration. This is the logical outcome of a scenario in which making a database fault-tolerant with 6 copies across three availability zones with continuous backup is now merely a product feature instead of a full time job or jobs.”
Original source: Whither the DBA
What’s a DBA to do in a cloud world where platform as a service and PaaS-like automation seemingly removes much of the need to constantly car for pet databases? Well, there’s still troves of existing databases left and, really, things aren’t that perfect in cloud-land. I spoke with Klint Finley on this topic last week for his story on Heroku. He asked, “are the days of the DBA numbered? to which I responded:
I don’t think the DBAs days are numbered just yet. Last I checked, the US bureau of labor statistics is actually predicting an increase, if that’s anything. DBAs definitely need to learn new technologies and be less gruff about helping developers out.
Consistently, I see developers driving the use of cloud across the market (ask any vendor what their cloud stuff is use for and it typically amounts to delivering custom written applications: developers) which means DBAs need to start talking with developers more. The other important thing to realize is how much "traditional” IT exists out there now. I can’t figure out how to calculate it (yet) but I feel like we’re just scratching the surface of The Great Cloud Rewrite over the next 10 years in the enterprise space. That’s were DBAs have a strong hold and if they get cloud religion soon enough, they can set themselves up nicely.
DBAs actually have a wealth of knowledge and it’d be painful for developers to have to rediscover and learn all of that. That said, if all DBAs do is say “no, and it’s going to take 6 weeks,” they’ll be dead.
The plight of the DBA – Press Pass
It is not surprising that database startups are attracted to the DBaaS delivery model, with our own forecasts indicating that DBaaS revenue should grow at a CAGR of 86% from $150m in 2012 to $1.8bn by 2016. However, we have already seen a number of database startups that have failed to capitalize on this opportunity, and the cloud delivery model should by no means be seen as an easy option. To be clear: if you are struggling to gain adoption in an on-premises database market in which Oracle, IBM and Microsoft claim roughly 90% of revenue, don’t expect an easy ride in a DBaaS market in which Amazon accounted for more than 90% of all revenue in 2012, and is expected to increase its share of the market between now and 2016.
[T]his report should serve as a warning for other startups that are looking to the cloud delivery model to save them from an inability to gain traction for on-premises adoption (we won’t name names – the more realistic will know who they are, and the less realistic will assume we are talking about their rivals, anyway).
This is a nice overview of DBaaS from the new analyst house. if you don’t have access, try a trial and tell them Cote sentchya ;)
The cloud: where database startups go to die?