Over a million developers have joined DZone.

Don't Leave the Database Behind

DZone 's Guide to

Don't Leave the Database Behind

Yaniv Yehuda discusses keeping the database at the forefront of the minds of DevOps to fill the need for source control, automation, security, and reporting.

· DevOps Zone ·
Free Resource

The DevOps Enterprise Summit in San Francisco is an extremely important conference which provides a measuring stick for the progress the DevOps industry has made over the past year. For our American readers, it’s “The State of The Union” of DevOps. The best and the brightest of the industry come together to talk trends, successes, challenges, to learn from one another and exchange ideas. It is also a place where those that are considering adopting DevOps come to learn about the resources offered. It was a perfect place for DBmaestro’s newly appointed EVP of North American Operations, David Rosi, to make his first public appearance as a member of the company.

In an interview conducted by Matt Hines from DevOps TV, Rossi talked about the database being left behind and how DBmaestro is changing perceptions:

“A couple of years ago, people were not thinking about the database. They were doing things manually, writing scripts, doing simple compare and sync analysis. They weren’t doing what they now need to do. We need to bring all those pieces together to be successful.”

Rosi, who is leading DBmaestro’s North America’s Operations based in the Boston area, addressed the increased attention the database has received at this year’s conference.

“The uptick that we’ve all seen in the use of tools on the application side is putting the database under more of a spotlight, so more and more companies realize they need to address the problem. Clients are starting to engage and show classic behavior in a market that’s starting to ramp up.”

Rosi understands the buzzwords associated with the DevOps culture; speed, scale, automation. However, he doesn't think that those things on their own are enough. He says,

“We looked at source control, for example, that’s different in a database world, and then the ability to automate what you now have trust in, so that you don’t have anybody playing around with your database. Having that security and reporting that’s going to tell you anything and everything you need to know about what happened with the database is the most important thing.”

Rosi agreed that a few years ago, security and automation were words that made people uncomfortable when seen together. But now, with the leveraging of automation early on, a lot of the problems that could become security headaches down the road, are going to be rooted out early on.

The full interview can be seen here.

devops ,database ,does 16 ,enterprise

Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

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

{{ parent.tldr }}

{{ parent.urlSource.name }}