Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Advancing Your API Strategy in an Infrastructure World

9 views

Published on

You can lead a horse to water, but you can’t make it drink. This is an accurate summary of what my initial journey of evangelizing API usage was like. In this talk I will take the audience through our journey, what worked, what didn’t work and what we learned along the way.

Published in: Technology
  • Be the first to comment

  • Be the first to like this

Advancing Your API Strategy in an Infrastructure World

  1. 1. Advancing Your API Strategy in an Infrastructure World Jaap Brasser – Developer Advocate
  2. 2. ▪ APIs? ▪ Who are we helping ▪ Open Sourcing our Efforts ▪ Closing the Loop ▪ Q&A
  3. 3. APIs?
  4. 4. ▪ Backup ▪ Cloud Data Management ▪ DR ▪ Test-Dev scenarios
  5. 5. ▪ APIs are relatively new in this space – Legacy Tooling – GUI ▪ Lack of understanding
  6. 6. ▪ Build from the ground up to be API-first – We like this ▪ API endpoints classified as internal – We do not like this ▪ OpenAPI Spec – We definitely like this
  7. 7. Who are we helping
  8. 8. Different roles
  9. 9. ▪ Simplify API Access – Provide SDKs and Modules ▪ Provide Use-Cases – Simple to implement – Well documented ▪ Documentation – Samples – Quick Start Guides – Video Tutorials
  10. 10. ▪ Provide access to code – GitHub ▪ Code ▪ Issues ▪ Allow to contribute – Clear contribution guidelines – Architectural documentation ▪ Provide contact – Social Media – GitHub
  11. 11. ▪ Provide examples – Showcase use-cases – Showcase integrations ▪ Simplify access – Provide web portal instead of GitHub
  12. 12. Open Sourcing our Efforts
  13. 13. ▪ Put API documentation on GitHub ▪ Create Quick Start guides ▪ Verified by technical writers ▪ Unexpected Contributions ▪ Created a separate portal
  14. 14. ▪ Unified labels ▪ Standardized README.md ▪ Created Quick Start Guides – For projects on GitHub ▪ Created video resources ▪ New Repository creation through Slack
  15. 15. Closing the loop
  16. 16. ▪ Provide clear paths to interact – Email – Twitter – Slack – GitHub ▪ Labels and organize issues – Provides opportunity for contributions – ‘first-timer’, ‘helpwanted’
  17. 17. ▪ Some handholding required – Not everyone is familiar with GitHub – Provide content to help people onboard ▪ Active project, active contributors – A lot of activity and contributions
  18. 18. jaap_brasser

×