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.
Service Virtualization Architect at a transportation company with 10,001+ employees
Real User
2020-10-22T23:30:06Z
Oct 22, 2020
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.
* By virtualization, for all dependent services, we are able to create isolated test environments. * 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. * We virtualize third-party paid services, as well as in-development services, to minimize costs and delays.
Learn what your peers think about Broadcom Service Virtualization. Get advice and tips from experienced pros sharing their opinions. Updated: November 2024.
Broadcom Service Virtualization offers a robust platform for isolating test environments by virtualizing dependent services, including fragile or in-development services. It’s a versatile tool widely used for API testing, virtual data creation, API marking from web servers, and supporting performance testing.\n\nUsers find Broadcom Service Virtualization incredibly efficient for creating and deploying virtual services as Docker containers that integrate seamlessly within Jenkins build...
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.
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.
The primary use case of this solution is for creating virtual services, creating API testing, and creating virtual data.
* By virtualization, for all dependent services, we are able to create isolated test environments. * 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. * We virtualize third-party paid services, as well as in-development services, to minimize costs and delays.
We use this tool to be more agile and deliver daily releases to production, shortening the development cycle.