Building a solid API is a challenge but getting our APIs to be adopted by a larger audience, we quickly realized that having solid SDKs is the key element. At Rubrik we have been developing SDKs to supplement our APIs for over 3 years and during this process we have been making sure our SDKs provide a seamless experience for end-users to consume. When breaking API changes occur during the development of our product. The key takeaways of this session are: * How to strategize SDK development against an ever-changing API * Securely open-source your SDK development process

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

10. Session
Management
No Direct
API Calls
Structured
Output
Different
Users

15. Ease of Updating
Build Tooling on SDK
Extend SDK based on tools

16. Open Source
Unit tests
Documentation

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

22. jaap_brasser
jaapbrasser