"High Tide" and "Neap Tide" usage pattern for Virtual Services - surprising insight from one of our customers
Bill_Hudacek 120000DFNF Visits (5950)
I caught up with a very major customer last week. They use AIT (Automated Integration Testing) and Service Virtualization (SV).
Back in February, during their first major implementation, they had about 250 active stubs (a.k.a., Virtual Services) deployed. Eventually that major effort got its real back-ends, and they un-deployed all of them!
Now, they're doing a major RESTful/Mobile effort with an estimated 150 Virtual Services. So there are only 150 Virtual Services deployed and running - not 400.
They have only 3-4 projects going right now, as they are still ramping up. But they told me this tide-comes-in, tide-comes-out will likely be their "best practice" pattern in the future, as it's working very well for them.
Still, more groups using the tools means the 'high water mark' will rise, too. They're already contemplating the need to expand their infrastructure to meet that demand, but a key takeaway is that there are efficiencies that will reduce the necessary footprint.
As a Technical Salespeson, I'd assumed that at most customers, Rational Test Control Panel and Rational Test Virtualization Server would manage 'almost every stub ever created'.
I thought this was really interesting. The value propostion for AIT & SV, which is already compelling, becomes even more so when you include how this can impact the cost of adoption and roll-out for enterprises of all sizes.