Content deleted Content added
m Dating maintenance tags: {{Ad}} |
added "Next Generation Service Virtualization" and "See also" |
||
Line 43:
The first step in the evolution from stubbing to service virtualization was the technology packaged in SOA testing tools since 2002.<ref>[http://www.gartner.com/id=356258 Parasoft's Web Service Testing Tool Should Aid Development] by Theresa Lanowitz [http://www.gartner.com Gartner], May 1, 2002</ref> The earliest implementations of service virtualization were designed to automate the process of developing simple stub-like emulations so that composite applications could be tested more efficiently.<ref>[http://searchsoa.techtarget.com/news/1283954/SOA-virtualization-gets-real SOA virtualization gets real] by Rich Seeley, SearchSOA, November 28, 2007</ref> As enterprise systems continued to grow increasingly complex and distributed, software tool vendors shifted focus from stubbing to the more environment-focused service virtualization.<ref name="virtual-strategy.com"/> While stubbing can still be completed through manual development and management of stubs, what has become known as "service virtualization" is completed by using one of the available commercial off the shelf (COTS) service virtualization technologies as a platform for the development and deployment of their "service virtualization assets".<ref name="ovum"/>
==Next Generation Service Virtualization==
The increasing popularity<ref>[https://trends.google.com/trends/explore?date=all&q=devops DevOps Google Trends]</ref> of [[Agile software development]] and [[DevOps]] created a demand for a new set of tools to deliver service virtualization. Practices like [[Continuous delivery]] and moving away from [[Mainframe_computer|mainframe]] and [[Monolithic_application|monolith]] development to more distributed [[Microservices|microservice]]-based architectures require new tooling <ref>[https://dzone.com/articles/the-future-of-service-virtualization-and-api-mocki Next Gen Service Virtualization Forum, 13th of September 2017]</ref>. The [[Comparison_of_API_simulation_tools|next generation tools]] are making it easier and more affordable to create an effective software delivery process by lowering the tool costs, decreasing accumulated bloat and no cumbersome licensing restrictions<ref>[https://www.thoughtworks.com/radar/platforms/big-enterprise-solutions|Thought Works Technolog Radar: Big enterprise solutions]</ref>.
Typical characteristics of the next generation tools:
* Lower cost or [[Free and open-source software|free open source]]
* Lightweight and [[KISS_principle|simpler]] in design, typically consisting of only one easy to use component instead of many complex components
* Highly extendable, scriptable and programmable using open source components and standards
The next generation of tools are also called<ref>[https://www.youtube.com/watch?v=Lesn4L3k6HE Tom Akehurst at the Next Gen Service Virtualisation Forum]</ref> [[Application_programming_interface|API]] simulators, API mocking tools, over the wire [[Test_Double|test doubles]] and tools for stubbing and mocking HTTP(S) and other protocols<ref name=technologyradarmoutebank>[https://www.thoughtworks.com/radar/tools/mountebank Thought Works Technology Radar Mountebank]</ref>. See the [[Comparison of API simulation tools]] for more details.
== See also ==
* [[Comparison of API simulation tools]]
==References==
| |||