Over a million developers have joined DZone.

Where Are All the DBAs in NoSQL?

DZone's Guide to

Where Are All the DBAs in NoSQL?

· Java Zone ·
Free Resource

Java-based (JDBC) data connectivity to SaaS, NoSQL, and Big Data. Download Now.

Earlier this month, Gartner released survey results that suggest that there aren't too many DBAs in the NoSQL space. Take a look: 

What's unclear, though, is the reason. The survey results might be questionable - selection bias, suggests Gartner - but the number is still surprising, and it has a number of people speculating. The folks a myNoSQL list a number of possibilities:

  1. DBAs see no value in NoSQL
  2. DBAs see no job security
  3. DBAs see a drop in their revenue with NoSQL
  4. DBAs are misinformed
  5. DBAs are change resistant (putting them in the later phases of adoption)

I’d go with a combination of 5 (explained mostly by 3) and 4.

The Orchestrate blog, on the other hand, suggests that the need for DBAs may be replaced in NoSQL with a different role, which DBAs may or may not gradually become:

Ten years from now, making sure your data is safe, well-managed, and accessible will be just as important as it is today. As developers continue to exert more control over an application’s lifecycle, and as DBaaS takes off, database administration will give way to data service administration. Whether the DBA role transforms into the DSA role or goes away altogether is beyond my guess.

Scalebase also weighed in, suggesting that DevOps may be to blame:

DevOps are the “cool” cloud guys who promote the trendy NoSQL revolution, in which the world is schema-less and much easier to maintain, implying that DBAs are no longer required.

So, what do you think? Assuming the DBAs aren't just shying away from surveys, what does this mean for NoSQL?

Connect any Java based application to your SaaS data.  Over 100+ Java-based data source connectors.


Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}