A database that is well incorporated can drastically affect your company in a positive way.
By Yaniv Yehuda
2017 is going to be a good year for DevOps for the database. Both development and operations teams have realized that managing source code, tasks, configuration, and deployments are incomplete if the database is the weak link. Also, the role of the DBA has evolved to the point where they are very involved in both development and operations, because a database that is well incorporated can drastically affect your company in a positive way.
For years, IT teams were not known to share information or cohesively work together. DevOps came along and successfully created an efficient, seamless, and a more error-prone application delivery process. The problem was that DBAs were overwhelmed with a significant increase in volume, because DevOps exponentially expedited the process at which applications were being released. Responsible for implementing, recording, testing, and managing all changes to the database, which is the last step in the release of applications, DBAs were met with some bitterness because they were blamed for delays in releases. Because of the significant workload increase, the database gained the reputation of the most vulnerable part of the application delivery process, often to the chagrin of the business executives, who were upset that glitch-filled apps and delays in releases were causing them to lose money.
As the database was incorporated into DevOps with automation, DBAs could deliver applications faster, reduce downtime, and enforce compliance.
