Several issues routinely come up in discussions about Service Virtualization. The first concerns whether you can run a virtual service in production. You can create an accurate representation of a production environment, but you wouldn’t run a virtual service in production because it doesn’t do the real work. For example, you can simulate a virtual service that does a credit check for dev and test, but in production, you would want to do the actual credit check.
The other issue that comes up on a regular basis is the handling of sensitive data. Virtual environments encapsulate all test data and have the ability to desensitize or obfuscate that data based on predefined patterns, keeping the data integrity intact. Once a behavior is captured inside a virtual service, there is no sensitive data left. Static desensitization design patterns also provide another level of sophistication when it comes to securing sensitive data.
We’d like to know about your experiences with service virtualization. What issues have you come across that you’d like to share with the group?
Service Virtualization in Production has a lot of merit and actually is used in enterprises TODAY. It all depends on the type of data. For example, Oracle Coherence provides object level caching at the middleware layer and caches information like product catalog, etc. If the actual service providing latest product catalog is down, the front-end shopping cart still works, because Coherence is able to provide the "cached" object response. "Caching" is one of the techniques used Service Virtualization too!
Wow... this is good on Middleware virtualization. However, can the object be updated in the run time.