Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

App Delivery Slowed by Manual Database Deployment Processes

DZone's Guide to

App Delivery Slowed by Manual Database Deployment Processes

Automating database deployments alongside application releases will accelerate application delivery.

· Database Zone ·
Free Resource

RavenDB vs MongoDB: Which is Better? This White Paper compares the two leading NoSQL Document Databases on 9 features to find out which is the best solution for your next project.  

Thanks to Robert Reeves, Co-founder and CTO of Datical, for taking me through a recent survey that found enterprise application teams are more hindered than ever by database teams to accelerate application updates. Additionally, the manual nature of database deployments create a bottleneck for business innovation and improving customer experiences.

According to The State of Database Deployments in Application Delivery survey, a research study conducted by Dimensional Research, 90 percent of enterprise application teams face pressure to release applications more quickly, 93 percent have application delivery challenges because of database deployments, and 71 percent report more than half of all significant application changes require database changes. Ninety-one percent of respondents report that database release automation would accelerate and improve the overall application release cycle.

A majority of enterprises are still manually reviewing, validating and deploying database changes. Ninety-three percent report challenges accelerating their database deployments, and 91 percent admit the need to rework database changes multiple times to make sure they are production-ready. Without database release automation, updating a mission-critical database to support an application change is a laborious, risky and time-consuming process that relies too heavily on human intervention.

“Because data is the most valuable asset an enterprise has, database deployments are a real challenge and must be managed very carefully. Sadly, database deployments have been widely ignored, in large part due to the high complexity and risk,” says Reeves. “These survey findings validate that if we continue the status quo, we will fail. It is beyond time to automate the database release process, just as we’ve done for the infrastructure provisioning and application release processes, to create a seamless and unified application delivery pipeline. As software professionals, we must ensure innovation and great customer experiences are brought to market faster for our companies.”

As application teams feel the increased pressure to release new, high-quality application innovation faster, enterprises are realizing the need to include the database in their overall application delivery strategy. Respondents cited the top three benefits of database release automation as: the ability for developers to more quickly find and fix errors in database changes (72 percent), reduced application downtime because of fewer bad database changes (66 percent) and improved application performance (60 percent).

“As the research reveals, database deployments are a bottleneck that slow down the business and put application performance at risk,” says Diane Hagglund, principal researcher, Dimensional Research. “The good news is that the data also shows that there are clear and tangible benefits for all teams when database release automation is adopted.”

To access and learn more about the survey findings, including the business impact of neglecting the database, as well as the benefits of automation database deployments alongside application deployments, download the full the report here.

Get comfortable using NoSQL in a free, self-directed learning course provided by RavenDB. Learn to create fully-functional real-world programs on NoSQL Databases. Register today.

Topics:
database ,app development ,app performance ,database deployment

Opinions expressed by DZone contributors are their own.

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

{{ parent.tldr }}

{{ parent.urlSource.name }}