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.

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.

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.

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

We use it for service virtualization. It is performing well. 

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

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.

It helps us to remove barriers that we have with dependencies on services that we don't own, or services that don't even exist yet, or services that are junky. It helps us to shift left and do our development earlier without waiting on those dependencies to be available.

We are into performance engineering. There are a lot of back-end systems that are sometimes unavailable, or there are a lot of various dependencies, and we're trying to get rid of those. That's one of the reasons we got into DevTest. 

And it's been helping us quite a bit now. We've been able to step out a lot of back-end systems. It's performed pretty well. There were a few hiccups, but we got in touch with the senior architects and they helped us out with fine tuning and, since then, it's been working out well.

It is throughout the STLC, so we actually have rights from the PoC or idealization from testing, development, and even production support where someone would like to use it for certification, or a sandbox perspective.