A walk across Service Virtualization world

One of the things that we hear the most in our daily basis are Service Virtualization, but probably you are not aware of this new thing. Do you? Do you know what we are talking when we talk about Service Virtualization? Ok, I’m going to try to explain to you.

Service Virtualization is the new wave to give more consistence, coherence, and a methodology to the mock/stub/dummy services you create so you don’t be stopped when you are developing.

Since the 2000’s the use of mocks or stubs on our development are a common practice, but that’s a internal technique we perform at our development team level (or even worse own machine level) so until now nobody have had a “methodology approach” to this practice to maximize the benefits from this practice and to improve the ROI.

The benefits of services virtualization are well known but I’m going to summarize them:

Parallel Development

Reliable Continuous Integration

Data Management for unusual test cases

Avoid using paid services

All of these benefits are the same when you use mocks or stubs, so you cut this dependency with the real back-end system, but the nowadays Service Virtualization have also this differences:

Better tools to create scenarios

Virtual Service Governance

Better ways to create your simulators

Originally published at alexandrev.github.io on February 20, 2016.

PSG Senior Architect at TIBCO Software with a focus on Cloud Development, Event Processing and Enterprise Integration

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store