Content deleted Content added
Line 47:
:"...applications are encapsulated as services and a distribution framework is sued to disseminate work across service instances. Service virtualization also allows the application developers to :treat services from different application domains as building blocks that can be assembled and reassembled to adapt to changing business needs"
:from {{cite book |last=Foster |first=Ian |date=December 2, 2003 |title=The Grid 2, Second Edition: Blueprint for a New Computing Infrastructure |url= |___location= |publisher= Morgan Kaufman|page=181 |isbn=978-1558609334|author-link= }} [[User:CodeCurmudgeon|CodeCurmudgeon]] ([[User talk:CodeCurmudgeon|talk]]) 22:54, 9 August 2017 (UTC)
:{{reply to|CodeCurmudgeon}} What is your take on the point of view that service virtualization is a type of a test double (an over-the-wire test double, or an out-of-process test double)? I think the answer to this question would inform greatly the tone of this page. I also think we have to consider the popularity of open source tools today when improving the article, and how they use the name, especially because they are [https://trends.google.com/trends/explore?date=today%205-y&q=service%20virtualization,wiremock,ca%20lisa,parasoft%20virtualize,readyapi|are getting increasingly popular]. Wiremock (the most popular open source HTTP mock today) calls itself a service virtualization tool as well as a mock (which is a test double) "WireMock is a simulator for HTTP-based APIs. Some might consider it a service virtualization tool or a mock server.". Mountebank (third popular open source tool) call themselves an over the wire test double and a service virtualization tool "mountebank is the first open source tool to provide cross-platform, multi-protocol test doubles over the wire (...) mountebank is the most capable open source service virtualization tool in existence". [[User:Wojtek-tp|Wojtek-tp]] ([[User talk:Wojtek-tp|talk]]) 17:22, 7 December 2017 (UTC)
== Issue re Next Generation ==
| |||