Broadcom Service Virtualization

Name: Broadcom Service Virtualization
Brand: Broadcom
Rating: 4.3 (3 reviews)

Leader

Broadcom provides semiconductors and infrastructure software for global organizations’ complex, mission-critical needs

Est 1961|Valuation $1764B

LinkedIn 446K|Website|Web traffic 4.0M|FTEs 33,000|HQ Palo Alto, California, US

MarketsTest Automation Performance Testing Observability Platform

Broadcom Service Virtualization screenshot

Published Oct 9, 2026

01Common complaints

1) Small teams or startups with simple dependency mocking needs - For teams that primarily need REST stubs in CI pipelines, open-source tools such as WireMock or MockServer may be more cost-effective and simpler to operate. 2) Organizations that cannot staff or enable service virtualization skills - Reviewers note success depends on tester skills and change management; without internal capability, adoption can stall. 3) Budget-constrained environments sensitive to enterprise licensing - Reviews and peer commentary indicate that licensing and total cost can be a barrier for small and mid-sized organizations. 4) Use cases requiring elastic horizontal scaling for very large test traffic loads - At least one reviewer reported scalability limitations. Buyers expecting very large-scale synthetic traffic should validate architecture, clustering, container scaling, and licensing constraints in a proof of concept.

Deal disqualifiers (poor fit)

Organization requires only basic HTTP mocking for a small set of APIs
Organization lacks capacity to maintain virtual service models as APIs evolve
Budget constraints that make enterprise licensing difficult to justify

Product lifecycle and version support

Broadcom issued an end-of-service announcement for Service Virtualization 10.6 effective March 1, 2023, recommending an upgrade to 10.7. This historical notice is relevant for upgrade planning and support timelines.

Complexity and maintenance burden

Setup time and operational complexity are noted in reviews and community threads.
Virtual services require maintenance when real service behavior changes, which adds operational overhead.

Scalability and compatibility gaps

Some reviewers report scalability or compatibility issues with particular hardware or application types; these limitations should be validated against specific use cases.

Security patch and vulnerability management

Broadcom publishes knowledge base guidance on vulnerability exposure for container images and instructions for obtaining fixed images; container image hygiene and patching are operational considerations.

02Why they buy

Differentiators supported by customer evidence

Service virtualization focused on enterprise integration scenarios with support for a broad set of protocols and scenario types; reviewers describe it as feature-rich and applicable for large-scale integration testing.
Enables earlier integration testing by providing controlled virtual dependencies, which can reduce reliance on live third-party systems.

Positioning claims requiring buyer validation

Vendor materials position SV as enabling continuous testing and simplified maintenance of virtual services. Buyers should validate maintainability and effort levels against reviewer feedback that updates can be time-consuming.

Competitor differentiators

Some competitors offer low-friction trial options (free editions) or leaner solutions that are easier to adopt for smaller teams.

03Field reports

Note on accessibility: Gartner Peer Insights was searched but no accessible Gartner Peer Insights SV review page was captured in the available sources. This section relies primarily on G2, PeerSpot, and Broadcom community threads.

Selected review summaries (platform and star ratings noted where available)

G2 (selected reviews): - A reviewer with a very positive rating described the product as central to their testing workflows and noted integration with various development tools. - A reviewer with a positive rating reported that integration testing could be performed earlier and that testing costs were reduced. - A reviewer with a positive rating indicated the product helped them avoid the need to provision actual servers for certain tests. Critical themes from reviews and community sources: - Initial setup and configuration can be time-consuming; reviewers report a non-trivial implementation effort - Licensing and cost are commonly described as less suitable for small and mid-sized organizations - Virtual services require maintenance when real service behavior changes - Some reviewers have reported scalability or compatibility limitations for certain hardware or application scenarios PeerSpot (aggregate signals): - PeerSpot reviews and featured snippets indicate usage for virtualization of third-party APIs during performance testing and cite cases of satisfactory support in specific accounts. PeerSpot's aggregated signals are directional and should be validated with hands-on evaluation. Broadcom community / support forums: - Community threads include operational troubleshooting (for example, VSE service stop delays and Windows service error cases), indicating real-world administration and reliability issues discussed by administrators. Interpretation guidance: review platform statements and customer comments for operational detail and validate key claims (performance, scalability, support SLAs) with proofs of concept and vendor documentation.

Telefónica Chile case study (vendor-published)

Broadcom-published case study reports: - A notable reduction in time-to-market reported by the vendor - A measurable reduction in total construction time reported - A small decrease in development costs reported - A significant reduction in infrastructure requirements for testing and trials reported - Implementation scope: a large development organization and a separate QA team - Scale of virtualization assets reported: a mix of virtualized services including several highlighted in the case study, additional services captured via proxy, and other simple WSDL-based services Critical evaluation: - These are vendor-published metrics; methodology, baselines, and attribution are not independently validated in the document. - The case study provides operational detail (team scale and counts of virtualized services) that supports plausibility for large enterprise scenarios, but buyers should request supporting metrics and independent validation during procurement.

04Best fit

Company size

Most consistent fit: very large enterprises (often thousands of employees) with multiple teams and complex integration needs.

Industries

Telecommunications
Financial services
Large IT services and consulting organizations

Roles and personas

QA automation leads and test architects
DevOps and platform engineering teams responsible for CI test environments
Integration architects (SOA/microservices)
Performance testing teams

Pain points the product addresses

Unavailable or unstable dependencies
Costly or fragile third-party environments
Long integration testing cycles
Difficulty reproducing defects due to unstable upstream services

Qualification criteria (strong fit)

Organizations that frequently block releases due to upstream integration instability
Multiple teams that need stable, reusable simulations
Need for protocol virtualization beyond simple REST mocks (e.g., mixed protocols)
Capacity to fund training or operate a center-of-excellence model for virtualization

05The pitch

What the product does (objective value proposition)

Broadcom Service Virtualization (SV) is an enterprise service virtualization platform (formerly CA Service Virtualization / part of CA DevTest Solutions) used to simulate dependent services and systems (APIs, middleware, legacy backends, third-party endpoints) so teams can run tests earlier in development without requiring access to those real dependencies to be available, stable, or cost-effective to call. In practical terms, SV creates virtual services that behave like real services (e.g., REST/SOAP endpoints, TCP/IP protocols), enabling: - Earlier integration testing (shift-left) - Parallel development by removing dependency bottlenecks - Performance testing without invoking real third-party systems - More deterministic automated tests by controlling dependency behavior Broadcom describes SV as a constraint-removal layer across the SDLC and CI/CD pipelines and positions it as a tool to support continuous testing; this framing is reflected in Broadcom training and marketing materials.

Target market and market positioning

Most suitable for large enterprises with complex integration landscapes, including: - Multiple upstream/downstream dependencies - Fragile or rate-limited third-party services - Legacy systems (including mainframe integration) that are difficult to provision for test - Requirements for integration and performance testing at scale Reviewer demographics and vendor-published case studies skew toward large enterprise and regulated industries (financial services and telecommunications appear commonly). Peer review platforms also indicate a research audience that is weighted toward larger organizations.

Get a comprehensive analysis of Broadcom Service Virtualization including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →

Published Oct 9, 2026

01Common complaints

Small teams or startups with simple dependency mocking needs

For teams that primarily need REST stubs in CI pipelines, open-source tools such as WireMock or MockServer may be more cost-effective and simpler to operate.

Organizations that cannot staff or enable service virtualization skills

Reviewers note success depends on tester skills and change management; without internal capability, adoption can stall.

Budget-constrained environments sensitive to enterprise licensing

Reviews and peer commentary indicate that licensing and total cost can be a barrier for small and mid-sized organizations.

Use cases requiring elastic horizontal scaling for very large test traffic loads

At least one reviewer reported scalability limitations. Buyers expecting very large-scale synthetic traffic should validate architecture, clustering, container scaling, and licensing constraints in a proof of concept.

Deal disqualifiers (poor fit)

Organization requires only basic HTTP mocking for a small set of APIs
Organization lacks capacity to maintain virtual service models as APIs evolve
Budget constraints that make enterprise licensing difficult to justify

Product lifecycle and version support

Broadcom issued an end-of-service announcement for Service Virtualization 10.6 effective March 1, 2023, recommending an upgrade to 10.7. This historical notice is relevant for upgrade planning and support timelines.

Complexity and maintenance burden

Setup time and operational complexity are noted in reviews and community threads.
Virtual services require maintenance when real service behavior changes, which adds operational overhead.

Scalability and compatibility gaps

Some reviewers report scalability or compatibility issues with particular hardware or application types; these limitations should be validated against specific use cases.

Security patch and vulnerability management

Broadcom publishes knowledge base guidance on vulnerability exposure for container images and instructions for obtaining fixed images; container image hygiene and patching are operational considerations.

02Why they buy

Differentiators supported by customer evidence

Service virtualization focused on enterprise integration scenarios with support for a broad set of protocols and scenario types; reviewers describe it as feature-rich and applicable for large-scale integration testing.
Enables earlier integration testing by providing controlled virtual dependencies, which can reduce reliance on live third-party systems.

Positioning claims requiring buyer validation

Vendor materials position SV as enabling continuous testing and simplified maintenance of virtual services. Buyers should validate maintainability and effort levels against reviewer feedback that updates can be time-consuming.

Competitor differentiators

Some competitors offer low-friction trial options (free editions) or leaner solutions that are easier to adopt for smaller teams.

03Field reports

Selected review summaries (platform and star ratings noted where available)

G2 (selected reviews):

A reviewer with a very positive rating described the product as central to their testing workflows and noted integration with various development tools.
A reviewer with a positive rating reported that integration testing could be performed earlier and that testing costs were reduced.
A reviewer with a positive rating indicated the product helped them avoid the need to provision actual servers for certain tests.

Critical themes from reviews and community sources:

Initial setup and configuration can be time-consuming; reviewers report a non-trivial implementation effort
Licensing and cost are commonly described as less suitable for small and mid-sized organizations
Virtual services require maintenance when real service behavior changes
Some reviewers have reported scalability or compatibility limitations for certain hardware or application scenarios

PeerSpot (aggregate signals):

PeerSpot reviews and featured snippets indicate usage for virtualization of third-party APIs during performance testing and cite cases of satisfactory support in specific accounts. PeerSpot's aggregated signals are directional and should be validated with hands-on evaluation.

Broadcom community / support forums:

Community threads include operational troubleshooting (for example, VSE service stop delays and Windows service error cases), indicating real-world administration and reliability issues discussed by administrators.

Interpretation guidance: review platform statements and customer comments for operational detail and validate key claims (performance, scalability, support SLAs) with proofs of concept and vendor documentation.

Telefónica Chile case study (vendor-published)

Broadcom-published case study reports:

A notable reduction in time-to-market reported by the vendor
A measurable reduction in total construction time reported
A small decrease in development costs reported
A significant reduction in infrastructure requirements for testing and trials reported
Implementation scope: a large development organization and a separate QA team
Scale of virtualization assets reported: a mix of virtualized services including several highlighted in the case study, additional services captured via proxy, and other simple WSDL-based services

Critical evaluation:

These are vendor-published metrics; methodology, baselines, and attribution are not independently validated in the document.
The case study provides operational detail (team scale and counts of virtualized services) that supports plausibility for large enterprise scenarios, but buyers should request supporting metrics and independent validation during procurement.

04Best fit

Company size

Most consistent fit: very large enterprises (often thousands of employees) with multiple teams and complex integration needs.

Industries

Telecommunications
Financial services
Large IT services and consulting organizations

Roles and personas

QA automation leads and test architects
DevOps and platform engineering teams responsible for CI test environments
Integration architects (SOA/microservices)
Performance testing teams

Pain points the product addresses

Unavailable or unstable dependencies
Costly or fragile third-party environments
Long integration testing cycles
Difficulty reproducing defects due to unstable upstream services

Qualification criteria (strong fit)

Organizations that frequently block releases due to upstream integration instability
Multiple teams that need stable, reusable simulations
Need for protocol virtualization beyond simple REST mocks (e.g., mixed protocols)
Capacity to fund training or operate a center-of-excellence model for virtualization

05The pitch

What the product does (objective value proposition)

In practical terms, SV creates virtual services that behave like real services (e.g., REST/SOAP endpoints, TCP/IP protocols), enabling:

Earlier integration testing (shift-left)
Parallel development by removing dependency bottlenecks
Performance testing without invoking real third-party systems
More deterministic automated tests by controlling dependency behavior

Broadcom describes SV as a constraint-removal layer across the SDLC and CI/CD pipelines and positions it as a tool to support continuous testing; this framing is reflected in Broadcom training and marketing materials.

Target market and market positioning

Most suitable for large enterprises with complex integration landscapes, including:

Multiple upstream/downstream dependencies
Fragile or rate-limited third-party services
Legacy systems (including mainframe integration) that are difficult to provision for test
Requirements for integration and performance testing at scale

Reviewer demographics and vendor-published case studies skew toward large enterprise and regulated industries (financial services and telecommunications appear commonly). Peer review platforms also indicate a research audience that is weighted toward larger organizations.

Get a comprehensive analysis of Broadcom Service Virtualization including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →