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

Can Legacy Software and Continuous Delivery Survive Together?

DZone's Guide to

Can Legacy Software and Continuous Delivery Survive Together?

Yaniv Yehuda poses and answers the question if legacy applications can benefit from continuous delivery.

· DevOps Zone
Free Resource

Download “The DevOps Journey - From Waterfall to Continuous Delivery” to learn learn about the importance of integrating automated testing into the DevOps workflow, brought to you in partnership with Sauce Labs.

Dalibor Saroky asked in a recent article if Continuous Delivery can accommodate legacy software systems.

Small and medium-sized businesses in technology and media industries lead the way toward agile software delivery because they don’t have to deal with the technologies you might find at a multi-national bank or a global insurance company. Legacy applications carry with them legacy databases built on technologies that don’t lend themselves to instant deployment models, but there are tools and technologies designed to bridge these gaps.

If you run a large, revenue-generating application, says Saroky, there’s a good chance that you deal with massive databases from IBM or Oracle. It’s even more likely if your system supports business at scale that your application depends on several levels of middleware and multiple databases spanning a whole range of vendors and technologies. Until you can bring these systems along for the daily release schedule there’s still work to be done.

Saroky said that he’s focusing on databases because they are always the toughest aspect of enterprise release management, and they often present the most difficult challenges to moving toward fast-paced release cadences.

When your release timelines become constrained it’s always the databases that complicate everything. In a complex release you need to account for set up and tear down time when planning your testing environment’s database requirements. In a production-facing software release it is always the database operations that present the most risk in the process. Databases need to be migrated in one-off processes with little room for error, and during some releases database changes almost invariably call for production downtime.

Saroky also had some good news, that database vendors and other companies supporting tools such as Oracle and DB2 are developing novel solutions to make databases more agile. Test environments can now use data that is continuously masked from production data, and vendors are innovating with various approaches to block storage to make it easier to track database changes and perform rollbacks instantly.

Of course DBmaestro TeamWork has been breaking down silos between development and operations, enabling continuous delivery for the database for some of the largest corporations. I urge you to check out how DBmaestro can bring continuous delivery to your database by clicking here.

Discover how to optimize your DevOps workflows with our cloud-based automated testing infrastructure, brought to you in partnership with Sauce Labs

Topics:
devops ,continuous delivery ,legacy applications ,dbmaestro

Published at DZone with permission of Yaniv Yehuda, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

The best of DZone straight to your inbox.

SEE AN EXAMPLE
Please provide a valid email address.

Thanks for subscribing!

Awesome! Check your inbox to verify your email so you can start receiving the latest in tech news and resources.
Subscribe

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

{{ parent.tldr }}

{{ parent.urlSource.name }}