Download to read offline
Uploaded byapidays
apidays LIVE LONDON - Discovering API Version differences with ease by Jaap Brasser
The document outlines challenges and solutions related to discovering API version differences, focusing on various tooling and automation techniques. It highlights the importance of changelogs, reports on breaking changes, and the goal of generating comprehensive reports on version diffs and SDK changes. Key components include a comparison framework, use of OpenAPI specifications, and different roles involved in the process.
More Related Content
![[apidays Live Australia] How do you enhance customer experience through event...](https://cdn.slidesharecdn.com/ss_thumbnails/shiro-eventdrivenapis-customerenhancement-roundtable1-210922093028-thumbnail.jpg?width=640&height=640&fit=bounds)
Similar to apidays LIVE LONDON - Discovering API Version differences with ease by Jaap Brasser
apidays LIVE LONDON - Discovering API Version differences with ease by Jaap Brasser
- 1. Discovering API Versiondifferences with ease October 27 & 28, 2020#APIDays
- 2. Tweets Codes Works Does Likes jaap_brasser jaapbrasser Developer Advocate Blogger, Speaker,Coder Cloud Automation & Security
- 3.
- 4. Use cases • Backup •Cloud Data Management • Disaster Recovery • Anomaly detection • Test / Dev scenarios
- 5. Rubrik API Architecture Authentication: •Basic (user/pw) • API token Rubrik UI same logic applies API Abstraction: • SDK • Plug-in • Automation tool Consumes 3rd party APIs: • Amazon S3 API • Blob Service REST API Spray - framework for building REST/HTTP- based integration layers Spray-can - lightweight HTTP server that handles REST methods Spragger - generates code using OpenAPI spec REST API *OpenAPI spec Versioned: /internal /v1 /v2
- 6. Who are wedealing with Different roles, different expectations
- 7. Downstream Dependencies Browser &Desktop Tools Chrome Developer Tools Automation Tools Playground Direct SDK Abstraction Plug-in https://build.rubrik.com
- 8. The Challenge Jukan TateisiUnsplash
- 10. Challenges • Readingchangelogs • Different product versions • Downstream languages • New functionality
- 11.
- 12. Ideal Scenario • Generatereport on version diffs • Report breaking changes • Moved endpoints • Changes in status / body / param • Report on SDK changes
- 13. What we’ve built Eternallywork in progress Comparison Framework Swagger Definitions Downstream SDK Analysis Reports
- 14. Lessons Learned Changelogs are notfun 01 Automation is fun 02 Edge cases 03 New functionality 04 Integrate in processes 05
- 15.