Unlocking collaboration with Internal Developer Portals and Marketplaces - Democratizing API Access

Transcript

1. Unlocking Collaboration with Internal Developer Portals & Marketplaces: Democratizing API Access 1
2. codecentric AG Hoher Wall 15 44137 Dortmund Telefon: +49 (0) 151. 10 86 70 74 Daniel Kocot Head of API Experience & Operations AsyncAPI Ambassador daniel.kocot@codecentric.de www.codecentric.de Innovative - Trustful - Competent - Pragmatic 2
3. 3 Collaboration
4. 4 Collaboration in API context
5. Providers and Consumers Consumers Provider Asking for something Receving something
6. Consumers
7. General Definition The term consumers refers to a software application, service, or program that utilizes and interacts with another entity's API to access and consume its data, functionality, or services Just like a consumer in a market context purchases good or services, an API consumer interacts with APIs to integrate their features and capabilities into their own applications or systems
8. 4 Characteristics of a consumer NEEDS WISHES TRIGGERS IDEAS
9. Needs Data Integration Reliability Scability Documentation
10. Wishes User-Friendly Integration Customisability Real-time Updates Support and Assistance
11. Triggers User Demands Positive Reviews
12. Ideas Innovation New user experiences New business opportunities
13. 3 Shapes 13 Driven by technology Driven by business Driven by innovation
14. Places to collaborate 14
15. Let’s talk about Internal Developer Platforms and Marketplaces
16. 16 Internal Developer Platform
17. Consumer shapes in reference to IDP 17 Driven by technology Driven by innovation
18. Focus Persona: Technology 18
19. Focus Environment: Internal 19
20. Goal: Developer Success 20
21. Marketplace
22. 22 API Marketplace
23. Consumer shapes in reference to Marketplace 23 Driven by business Driven by innovation
24. Focus Persona: Business 24
25. Focus Environment: External 25
26. Goal: Business Success 26
27. What does this mean for API Access?
28. In short, it must be simple! 28
29. But reality looks different 😉 29
30. APIs are still a complex thing to handle 30
31. The implementation side is hard 31
32. It doesn’t only help if we are using an IDP or Marketplace 32
33. There’s only one persona to understand the offered APIs in all detail 33
34. The persona mostly driven by technology 34
35. Goals to achieve Easy first access with security in mind Champion people driven by technology Provide smooth data transfer Direction of external monetisation
36. Easy first access with security in mind Establish an overall access concept from the beginning Every stage is production Create tutorials and trainings how to access Implement sandbox technology covered by security
37. Champion people driven by technology Ask for specific needs Involve the champions as early as possible Build the story around them Support their drive of innovation as much as possible
38. Provide smooth data transfer
39. Definition Data Product Value Creation Algorithm-Driven Integrated Output Iterative Development
40. Definition Data Contract Defined Schema Data Governance Interface Agreement Version Management
41. Definition API Product Exposure of Capabilities Standardized Interface(s) Authentication & Authorization Monetization & Analytics
42. Provide smooth data transfer Align data products with API products Use or build up a data product specification Use data contracts to stabilise the transfer Every data product should be available with every API styles the organisation is providing (if possible)
43. Direction of external monetisation THINK ABOUT BARTER AT FIRST CREATE A SIMPLE BILLING MODEL PRESENT ADDITIONAL VALUES
44. Conclusion Only the technology driven shape of consumers is of interest We have to build the whole story around them For access it's not enough to use a portal or marketplace
45. 45 codecentric AG | Hochstraße 11 | 42697 Solingen Creating the digital future together. Thank you!
46. References Cover Slide: Photo by Gary Butterfield on Unsplash Slides 21 and 22: Photo by hoch3media on Unsplash