Continuous Delivery and Service Virtualization – What does it do for me?

Writing on WhiteBoard

Continuous Delivery essentially does what it says on the tin… adopting a continuous delivery approach to your development, you choose when you wish to deliver apps to your customer. This really means that at all times, your application is ready to be delivered and installed by your customers.

In today’s fast moving world, customers expect incredibly reactive support for their apps, otherwise they will simply install a different app to achieve the same thing.

If there is a new feature to be made available in an app, similarly they expect it to be delivered in days, or weeks at a minimum.

Reliable Testing Platform

This cannot easily be achieved with typical waterfall development methods as it simply takes too long to release software.

 To achieve this level of support for your customers you need to have a rock solid testing platform, so that when a change is made to the code in the app, the change itself is extensively tested while an entire slew of regression tests are also run to ensure that the new change has not unhinged something else in the system.

In this way, once the tests have completed, you can be satisfied that the changed app can be delivered to your customers.

Service Virtualization enables the agile testing process.

This can be achieved by totally automating the testing process and ensuring that the development and testing teams are totally integrated such that development and testing is done in an agile way.

Service Virtualization enables this agile and automated testing to take place in a cost effective way. As can be seen from the following comparisons of what can be considered traditional development life cycles versus agile development lifecycles that continuously deliver, there are cost advantages to this  and service virtualization is a massive contributor to that process.

 Below is an outline of the traditional App Delivery Cycle v. App Delivery Cycle with Service Virtualization.

 Ost CIDiagram 001


Osti CIDiagram 002


What are your thoughts on the general shift towards CD, SV and agile methodology? let us know in the comments section below.


Click here for a deeper dive into our solutions

Written by : John Power