
Broadcom Service Virtualization
Continuous integration tools
Service virtualization software
DevOps software
CI/CD tools
- Features
- Ease of use
- Ease of management
- Quality of support
- Affordability
- Market presence
Take the quiz to check if Broadcom Service Virtualization and its alternatives fit your requirements.
Contact the product provider
Small
Medium
Large
- Information technology and software
- Media and communications
- Real estate and property management
What is Broadcom Service Virtualization
Broadcom Service Virtualization is a service virtualization and API simulation tool used to create virtual services that mimic dependent systems for development and testing. It helps teams test applications earlier by isolating dependencies such as mainframes, third-party APIs, and unavailable services. Typical users include QA, DevOps, and development teams building automated tests and CI/CD pipelines that require stable, repeatable environments. The product focuses on protocol/API virtualization, test data handling, and integration into enterprise testing workflows.
Strong dependency simulation
It virtualizes services to reduce reliance on unavailable or costly-to-access systems during development and testing. Teams can model behaviors for complex dependencies and run tests in controlled conditions. This supports earlier testing and more predictable automated pipelines when upstream systems are unstable. It is commonly used in enterprise environments with many interdependent applications.
CI/CD pipeline integration
It supports automation use cases where virtual services are started, configured, and used as part of build and test jobs. This helps teams run integration and regression tests without waiting for shared environments. It fits workflows where test execution needs consistent endpoints and deterministic responses. The product aligns with DevOps practices by enabling repeatable test environments.
Enterprise testing ecosystem fit
It is positioned to work alongside broader testing and quality management practices used in large organizations. Teams can use it to standardize how dependencies are simulated across multiple projects. This can reduce duplicated mocking efforts across teams and improve reuse of virtual assets. It is often adopted where governance and repeatability are required.
Setup and modeling effort
Creating accurate virtual services can require significant upfront work to capture traffic, define behaviors, and maintain models as APIs change. Complex dependency chains increase the effort to keep simulations aligned with production. Teams may need specialized skills to build and troubleshoot virtual services. This can slow initial rollout compared with simpler mocking approaches.
Licensing and cost complexity
Enterprise service virtualization tools are typically licensed commercially and can be costly at scale. Budgeting can be challenging when multiple teams need concurrent environments and extensive protocol coverage. Organizations may need to manage license allocation across CI agents and test environments. This can be a barrier for smaller teams or broad adoption.
Operational overhead in pipelines
Running virtual services in CI/CD adds infrastructure and lifecycle management tasks (provisioning, configuration, data resets, and monitoring). If not standardized, teams can experience drift between virtualized behavior and real services. Maintaining parity often requires ongoing collaboration with API owners and continuous updates. This overhead can reduce the simplicity of pipeline maintenance.
Seller details
Broadcom Inc.
Palo Alto, California, USA
1961
Public
https://www.broadcom.com/
https://x.com/Broadcom
https://www.linkedin.com/company/broadcom/