What is most valuable?
I think the most valuable feature is the ability to quickly create simulations of APIs that you use to disconnect you from your dependencies as part of your testing process.
We've really done two different scenarios. One is the creation of a new API. We were able to create a simulation before we ever wrote a line of code, and so all of our customers who would use that gave us direct feedback very quickly. In a performance environment, we have lots of dependencies, lots of services that we talk to. Having the simulations gave us the ability to run test when we want rather than when they're available.
What needs improvement?
The things that we're interested mostly are deployment kinds of capability. We would like to deploy these simulators as part of our continuous deployment process. We would like to be able to auto-deploy them as part of the test mechanism to help test teams without having to set up the infrastructure in advance.
For how long have I used the solution?
What do I think about the stability of the solution?
We've had no issues with the stability of the solution, had no problems at all in the six months we've had it deployed.
What do I think about the scalability of the solution?
One of the requirements that we had early on was the ability to handle high transaction rates. Our target was 700 transactions a second. We were just able to prove with our mix of services over 750 so very, very comfortable.
This is one development group. We have lots of different groups that are standing at the doorway to get in. It's a very exciting time.
How are customer service and technical support?
We didn't use technical support during the evaluation. We've used it a lot since, mostly to try and fix things that we didn't quite understand properly, not bug fixes.
Which solution did I use previously and why did I switch?
Listening to our executives, one of the key difficulties that the development teams were having is the ability to test faster, so they can't deliver content faster to our customers because they can't test fast enough mostly because of these dependencies and the outside suppliers. Having a service virtualization solution gives us the ability to disconnect ourselves from our suppliers and those blocking dependencies, allows us to go faster.
We're not really KPI-driven. It's really can we allow the team to test without the dependencies where they weren't able to do that before?
How was the initial setup?
One of the reasons we picked the product was it was easy to set up. We signed our contract at the end of May, and we had our production instance up and running in the second week of June, so it was very easy to set up and it's been running solid since.
What other advice do I have?
We really disconnected ourselves from the IT department. They run the infrastructure. It's then very stable and performant. Most of the administration is done by the engineering team itself, product engineering.
This solution is very valuable in terms of being able to speed up. One of the primary capabilities was the ability to consume it by our teams. How hard is it to learn? How hard is it to set up? Of the three vendors in the evaluation, the CA Service Virtualization was the easiest license model and the easiest to stand up and configure.
I've never really given anybody a 10 so I give them a 9. It's done everything it said it would do. We've got great consumption, early acquisition of the product. Support has been fantastic as we hope it would. The user interface is easy to learn. All of the things we set out as objectives have been met in the primary deployment.
CA Service Virtualization is an amazing solution, very easy to use, easy to train others on how to take advantage of it. I'd say jump on it.