API SDK Development – Lessons Learned
0 likes818 views
The document outlines lessons learned from developing an API SDK, focusing on the challenges faced, such as integrating new API endpoints and managing contributions. Key takeaways include the importance of establishing coding standards, enabling contributors, and improving integrations and tooling. The author emphasizes the need for an API-first approach while addressing security and automation in the development process.
1 of 22
Download to read offline
More Related Content
What's hot (20)
Ad
Similar to API SDK Development – Lessons Learned (20)
Ad
More from Pronovix (20)
Recently uploaded (20)
API SDK Development – Lessons Learned
- 1. API SDK Development - Lessons Learned Jaap Brasser – Developer Advocate
- 4. ▪ Rubrik APIs ▪ The Goal ▪ Challenges ▪ Lessons Learned ▪ Questions
- 5. Rubrik APIs
- 6. ▪ Backup & Restore ▪ Cloud Data Management ▪ Disaster Recovery ▪ Test-Dev scenarios ▪ CI/CD Integration
- 7. ▪ APIs are relatively new here – Legacy tools, executables – Custom modules or integrations – GUIs everywhere ▪ Lack of understanding of the API space
- 8. ▪ Build from the ground up to be API-first ▪ Good! ▪ API endpoints classified as internal ▪ Not good! ▪ OpenAPI Spec ▪ Excellent!
- 9. The Goal
- 15. Ease of Updating Build Tooling on SDK Extend SDK based on tools
- 17. The Challenges
- 18. Team Enablement Open Source Management Bugs in APIs New API versions
- 19. Security of SDK Automate everything Branching and Releases
- 20. Lessons Learned
- 21. Create coding & contribution standards 01 Enforce Unit Tests 02 Enable the contributiors 03 Integrations & Tooling improvements 04 Issues and Contributions Time! 05 Do not automate everything 06