The 2020 DBA: A Look Into the Future

database administrators, or dbas, are responsible for the performance, integrity, and security of a database. their responsibilities include building, tuning, and updating new systems. the growing popularity of devops and tools like virtualization, cloud data storage, and microservices, means the role of a dba is changing. but despite their evolving roles, devops has actually made database administrators more relevant than ever before.

automation has brought an end to many of the mundane and repetitive tasks that dbas were once responsible for. nosql databases provide a mechanism for storage and retrieval of data that does not require a pre-defined schema. the once-lengthy process of adding new servers has been reduced to clicking a few buttons. even relational database companies are pushing customers toward “desktop-as-a-service” in which the back-end of a virtual desktop infrastructure is hosted by a cloud service provider.

but daas has been embraced for a fraction of what companies do and most companies don’t keep their mission-critical information in the cloud. additionally, not everything can be automated at this point. for example, there aren’t many tools around for finding and fixing slow queries or picking the best shard keys . on top of that, automation has made data environments more complex for anyone without specific administration expertise.

not only are environments more complex, but the job of maintaining them as a dba is more difficult than ever, as well. where once knowledge of oracle and microsoft sql server might have been enough to become a sufficient dba, today it’s not uncommon to find stacks with fifty different integrated technologies. frameworks and software like hadoop, kafka, and elasticsearch are vastly different and a dba must know which one to use — and in which situation to use it.

databases have become so muddled by their nuances and components that it’s sometimes impossible to characterize exactly what a database is. apache kafka , for example, has the properties of a database in that it shuffles real-time data, but it is not a database. dbas have the flexibility and understanding necessary for keeping up with these specific tools that should not be put in the hands of unqualified workers.

the next generation of dbas will be less involved in the hardware and software stack. they will still need to be database intensive, but not exclusively. instead, the dba will focus on tasks like capacity planning, and they will need to know when to provision more servers and when to retire them.

just as the definition of what a database is has become less clear, so too has the role of dba. with the spread of devops, more people within an organization have greater knowledge of the database and what makes it tick. given how much time people are required to spend with their own stacks of data, isn’t everyone becoming something of a dba at heart?

how has the role of dba changed in your company? let me know what you think in the comments!