Broadcom Service Virtualization Reviews

We use it for the virtualization of third-party APIs for performance testing.

Our second use case is related to the virtualization of TCP/IP protocols for third-party terminal insurance, which is used for insurance clients.

In the case of the virtualization of TCP/IP protocols for third-party terminal insurance, there was a device terminal, which was interacting with the application via the TCP/IP protocol. Most of the tools don't support that, but we were able to achieve it using Broadcom Service Virtualization.

The primary use case of this solution is for creating virtual services, creating API testing, and creating virtual data.

The most valuable features are the recording and creating of virtual services. Especially in creating IBM MQ virtual services through recording.

We mark up several APIs from web servers, JMS, and MQ Services with this solution. We use it to support our performance testing. Some of the virtual services that have been built by this solution will support somewhere around 2000 to 3000GPS perfectly.

There are several areas that are easily configurable. A person, without having a lot of development experience, should be able to perform most of the functions.

There are many different features available to build services with adequate response times, recording of visitors.

1. By virtualization, for all dependent services, we are able to create isolated test environments.
   
2. We virtualize fragile services and deploy them with the 'Failover' mode so that we can fall back to the VS in case the real service returns an error.
3. We virtualize third-party paid services, as well as in-development services, to minimize costs and delays.

In short, we are able to save a lot of valuable time. Testers and developers no longer complain about not having access to dependent services. We don't have to share/reserve resources or worry about our development being blocked by unavailable services.

We use this tool to be more agile and deliver daily releases to production, shortening the development cycle.

It hasn't matured enough yet to provide good prospects; we are still in the process of implementation. I can't tell you if anything in the process has improved or not, but the objective is to use this DevTest tool to shorten the development cycle. It hasn't proved itself yet. We've had it for a short time so I can't tell you if we succeeded or not.

On the testing side of the functionality, there are a few things that are missing. For instance, a comparative report. But since it's open source, we can add the extension and we do this by ourselves.

The ability to do parallel development and testing reduces our costs for duplicating environments, improving the productivity of our developers, and bringing products faster to market. 

As far as the next version of it is concerned, probably some additional lightweight, portable elements. For instance, we would like to not have to rely on deploying things to a server, be able to carry it and make it more portable (maybe through the mobile devices), etc. Some of the mobility aspects are what we are looking for, and I do not mean running it on a mobile device when I say mobility, but being able to port it between workstations, and being able to take it and work with it at a smaller scale.

Virtualizing mainframe systems. Reducing dependency on mainframe capacity and availability, which is a major roadblock for us right now.

The virtualization is primarily performed by eliminating the back end mainframe system. So we can read out our API traffic to the virtualized system. Basically, we don't have to use the mainframe while our service is virtualized.

It helps us with work/life balance. If we didn't have that CA Service Virtualization, we would have to run our performance tests during the night, because that's when the mainframe is least used. For our team members it helps them to maintain a better work/life balance, as they can execute their tests in the daytime so they don't have to spend the weekends and nights doing so.