The Magic Behind Faster API Development, Testing and Delivery with API Virtualization
1 like432 views
The document discusses API virtualization as a solution for faster API development, testing, and delivery, highlighting techniques such as static and dynamic mocking to simulate API behavior. It outlines various use cases, including development shortcuts, component isolation, and performance testing, while emphasizing the benefits of minimizing impact on external systems. Additionally, considerations for creating and managing virtualized APIs are presented, addressing scenarios where API virtualization is particularly beneficial.
More Related Content
Similar to The Magic Behind Faster API Development, Testing and Delivery with API Virtualization (20)
More from Nordic APIs (20)
The Magic Behind Faster API Development, Testing and Delivery with API Virtualization
- 1. THE MAGIC BEHIND FASTER API DEVELOPMENT,TESTING AND DELIVERY WITH API VIRTUALIZATION Presented by: SmartBear CTO, OAI Chairman, Ole Lensmar @olensmar | @SmartBear
- 2. Page @SmartBear The path to APIVirtualization starts with…
- 3. Page @SmartBear Stubbing / Static Mocking • Static responses • Semantically correct • No logic • Payloads generated from schemas or examples • Code or generated from metadata • Usage: Client and Test development
- 4. Page @SmartBear Dynamic Mocking (Simulation) • Dynamic responses • Based on input • Re-use input in output • Scripting • Data-driven / Data-generation • Simulate state • Usage: Scenario Testing, Development
- 5. Page @SmartBear APIVirtualization • Runtime behavior simulation • Runtime management • Redirect traffic to Virtual APIs dynamically • Access control • Deployment • Test execution integration • Assertions on incoming content • Usage: Integration / Scenario Testing, Load Testing, Development
- 6. Page @SmartBear A couple of use cases…
- 7. Page @SmartBear Bootstrap Development Virtualized API Generate from spec or with tools Client Development Test Design Integration Development • Shortcut the API development cycle / process • Bridge dependencies between roles / teams • Enable early feedback on API design / implementation Development
- 8. Page @SmartBear Component Isolation during Dev and Test Component in dev or test Test Execution (automated or manual) 3rd party APIs (virtualized) Other APIs (virtualized) Legacy Systems (virtualized) Development • Simulate (un)expected behavior • Minimize impact on and usage of external systems • Assert usage of external components
- 9. Page @SmartBear Provide Sandbox for API consumers Hardware / Software Solution API Virtual API Evaluate Integrate Integration Test • Provide simulations of different usage scenarios • Minimize usage / exposure of real system • Understand how customers interact with API
- 10. Page @SmartBear Performance Testing with API dependencies Solution under test Load Test Execution (automated or manual) 3rd party APIs (virtualized) Other APIs (virtualized) Legacy Systems (virtualized) • Simulate (un)expected performance in external systems • Minimize impact on and usage of external systems • Triage Performance bottlenecks
- 11. Page @SmartBear Internal Corp Web app Corp App + API API API API Device API Device IoT Device IoT Device API API API Component Evolution in complex architectures • Enable independent evolution of services by simulating external dependencies as services move through lifecycle
- 12. Page Virtualization across the API Lifecycle Design Build Test Deploy Manage Static mocking Dynamic mocking API Virtualization @SmartBear
- 13. Page @SmartBear How create virtualized APIs?
- 14. Page @SmartBear Create from API definition / contract • Swagger/OAS, RAML, API Blueprint, WSDL, WADL, etc. • Integrated schemas or examples for payload generation • Static Mocking often integrated in design tools • Dedicated tooling common
- 15. Page @SmartBear Create from captured API usage • Convert intercepted API responses into virtual APIs • Log-files – limited payload data • Captured traffic often needs to be “refined” • Removal / change of headers • Removal of sensitive data • Added logic for propagation of values • Record non-functional aspects • Response times, latency, etc. • Record SSL using MITM with dedicated certificate
- 16. Page @SmartBear Refine with dedicated tooling • Add complex logic for request dispatching • Add data-driven payloads • Simulate non-functional behavior • Add assertions for validating requests • Pass-through to actual APIs as appropriate
- 17. Page @SmartBear Considerations • How will virtual APIs be used and managed • Local / Team / Enterprise • Technical proficiency of maintainers • Scripting / coding requirements • CI-Integration • How redirect API calls to virtualized APIs • Access control (internal / external) • Reporting and Governance
- 18. Page @SmartBear Virtualising Async APIs • Domains • Web: Webhooks, AsyncSOAP, Websockets • Legacy: JMS, MQSeries, etc • IoT protocols: MQTT, AMQP, XMPP, etc • Virtualization Needs • Simulate both sender and receiver of events • Coordinate decoupled message flows / transactions • Simulate both functional and non-functional behaviour • Challenging to coordinate orchestrated components
- 19. Page @SmartBear APIVirtualization – do you need it? • Local development and basic component testing –> Probably not • For providing Sandbox environments -> Probably • Collaborative evolution and testing of APIs with low number of dependencies -> Maybe • The same – but with high number of complex dependencies -> Probably • For simulating both functional and non-functional behavior in complex distributed API-based solutions / architectures -> Definitely