Right now, the best platform for Micro Focus Service Virtualization is the Windows environment. Windows is somewhat less stable than Linux, and because Windows is not as stable, the maximum stability you can have with Micro Focus Service Virtualization is 70%.

The product is stable. Sometimes there is an issue with the operating system, but normally, the product itself is stable enough.  

Service Virtualization is not stable in the market right now, if you really check the technology behind it.

We majored a system in an OSI reference model, so we skipped most layers as well as apps and session tiers where traffic is recorded.

I have a web server, an application server, a file server, and a database server that takes a normal user work floor. If a user comes, they log in, and the traffic flows in. Service Virtualization allows you to record it, and simulate the way it's supposed to be simulated in a real environment.

I would like to define the stability of a critical system, for example, with the mainframe. We are still struggling with how to create APIs in Service Virtualization to talk with our AS/400 system and with a couple of CRM systems that are so proprietary that you cannot even record a set out of them.

Protocols are constantly changing. If you asked me ten years ago how many protocols I was using, I could give a number.

However, today, it's not X, it's X plus Y, plus Z. This keeps growing, and the product, and the companies who are making the Service Virtualization product are unable to keep up that pace.

The stability of the product, it’s still a work in progress. There are sometimes that, just honestly I do have to go onto the system and, just the other day we had one service that had been running for months with no problem, and then for some reason it just stopped working. I could’ve reached out to support to get an answer. They’re usually pretty responsive and get it solved for me pretty quickly, but for the sake of expediency because we were blocking people I had to go in and remove and rebuild service virtual-endpoint. The good thing is it took me 30 seconds to do it, the bad thing is I had all my data that I had saved gone. I could get it back, it’s not a big deal but-so stability wise it’s not bulletproof but I haven’t had a major outage until the other day of that one service. That hasn’t caused any issues, there’s been no ripple effects because of that.

In the four months we've used it, I've had no stability issues with very good load on the platform.

We have not encountered stability issues with the newer versions.

The stability seems to be very solid. Our boxes are idle, oversized, and don't have memory leaks. When they're in use, they're very stable without any performance of memory spikes.

Early on though, we saw some stability issues with the design that would occasionally crash. If we used it for six straight hours with many projects open, it had stability issues. But the design has been improved and the current version seems very stable, both on the server and design side.

The latest version, 3.81, is pretty stable.

The service virtualization tool is perhaps one of the newest tools compared to its competitors, but it also means it has a very high degree of energy in it. From our experience, we have put more than 20 enhancement requests for the service virtualization platform and to the Micro Focus R&D team, based in Prague in the Czech Republic, who has been very approachable. They have taken our suggestions and they have actually implemented our enhancement requests, which is very nice to know.

It's very stable.

Sometimes it stops working after switching remote and local servers.

With the new models of HPE 380 and similar models that HP's released, firmware upgrades, software upgrades on side the end-user experience with the virtualization engines has become a lot easier. The amount of time and effort for engineers to actually go and deploy those new drivers' software and firmware have been reduced from days/weeks to hours, making it far easier for any end-user to actually go and deploy a firmware update on their hardware infrastructure, without having to do an enormous amount of mitigating testing.

Stability-wise, this product is very good.

The stability is good. I would say it's okay.