apidays LIVE Hong Kong - Embark on a journey of API Management Maturity by Helal Nouri
•Download as PPTX, PDF•
0 likes•40 views
apidays LIVE Hong Kong - The Open API Economy: Finance-as-a-Service & API Ecosystems Embark on a journey of API Management Maturity Helal Nouri, Senior API Consultant at Rabobank
Recommended
More Related Content
Similar to apidays LIVE Hong Kong - Embark on a journey of API Management Maturity by Helal Nouri
Similar to apidays LIVE Hong Kong - Embark on a journey of API Management Maturity by Helal Nouri (20)
More from apidays
More from apidays (20)
Recently uploaded
Recently uploaded (20)
apidays LIVE Hong Kong - Embark on a journey of API Management Maturity by Helal Nouri
- 1. API Days Hong Kong Helal Nouri (Senior API Consultant) 8 October 2020 Embark on a journey of API Management Maturity
- 2. Rabobank at a Glance WhatWe Offer in the Netherlands Private sector lending to Food & Agri 38.4 Private sector lending to Trade, Industry and Services 80.6 Leasing 1.5 86 local Rabobanks 351 offices 1.9 million members 8.0 million private customers 0.8 million commercial customers Rabobank in the Netherlands Mission Growing a better world together Domestic Retail Banking (amounts in EUR billions) Situation on June 30, 2020 More than 9.5 million customers 8.8 million Dutch customers 0.7 million international customers Dutch Private Mortgages 187.6 Savings 131.9
- 3. Rabobank at a Glance International 38 countries Example value chain Farm inputs Farming Manufacturing/processing Trade Distribution Retail Food service private sector lending to Food & Agri €69.9 billion private sector lending to Trade, Industry and Services €35.3 billion Leasing €30.9 billion What We Offer Internationally
- 4. Rabobank Group’s Global Presence 4 Situation on June 30, 2020 Rabobank Group operates globally in 39 countries, including the Netherlands.Countries in which Rabobank has a minority interest or is engaged in projects are not included in the summary of countries in which Rabobank Group operates. 39 countries including the Netherlands
- 5. In the world of API’s we are interested in… 5 API Strategy API Design Governance Monetization API Culture API Ecosystem Observability API Security …API Culture API Ecosystem
- 6. Establishing an API Ecosystem upon an API Culture 6 Open & Shared Points of data & Content API ECOSYSTEM Bringing together Partners and Services Visible & Distributed API CULTURE … … … … Root Surface
- 7. Establishing an API Culture in different layers 7 Business Development Teams Management
- 8. 8 Management Level Establishing an API Culture
- 9. Establishing an API Culture on Management Level 9 Management API Strategies as boardroom considerations Treat API’s as evolving products Reach new customers Integrate Implement new business models Monetize on API’s Short term Long term
- 10. Design Live API v1, v2, v3… Deprecated Decommissioned Archived Deleted Test, Implement and Deploy Deprecated Decommissioned Archived Deleted Deprecate an API version Publish Replace Supersede API’s as Evolving Products with a Lifecycle
- 11. Business Level Establishing an API Culture
- 12. Establishing an API Culture on a Business level 12 Business Use API Roadmap Constant Experimentation Internal workshop and trainings Focus on API resources Empower Product Owners and Evangelist Short term Long term Accelerate Business Execution Provide Standardization
- 13. DevelopmentTeams Establishing an API Culture
- 14. Establishing an API Culture within DevelopmentTeams 14 DevTeams Set Quality Standards Right Infrastructure &Tooling Design First & ‘End-in mind’ Principle Plug & Play API Guild Short term Long term Constant Guardianship API’s as lipstick Assign API teams – not on project basis
- 15. Challenges with an API Culture 15 How to deal with lack of API Culture on the External Consumers’ side? Where to centralize API quality, standards and best practices? 1 2 How to stay Customer oriented while creating layers of standards? 3
- 16. Where we left off… How to establish an API Culture? 16 Open & Shared Points of data & Content API ECOSYSTEM Bringing together Partners and Services Visible & Distributed API CULTURE … … … …
- 17. Where we left off… How to establish an API Culture? 17 Open & Shared Points of data & Content API ECOSYSTEM Bringing together Partners and Services Visible & Distributed API CULTURE Constant Experimentation Focused & Aligned Empowered Community & interaction
- 18. Where we may conclude with… 18 API ECOSYSTEM API CULTURE API MANAGEMENT
- 19. 19 Thank you for your attention! Questions?
Editor's Notes
- Second day operations around API’s like monitoring, orchestration, observability. So much to talk about but we are interested here in the relationship between API Ecosystem and API Culture. Not talking about actual management of API’s inside a Management or Developer Portal but rather the encompassing whole. In many ways a retrospective as to how I have experienced it over the last 5 years.
- API Ecosystem is rooted upon an API Culture. We know what an API Ecosystem is and what its aspects are. But do we know what we need for an API Culture? My statement is: to have a living API Ecosystem, you need to develop an API Culture first.
- I strongly believe establishing API Culture happens throughout the organization in different layers. Starting from at the Top with Management, that includes Product Management, Business – or all the other departments. And finally centers around the Development Teams where the epicenter of an API Culture should reside. The relationship is not linear from Management towards Business and Development team. But interchangeably among the different layers.
- API Strategies: We are seeing API’s being elevated from just development techniques to Boardroom consideration and drivers of a business. This of course depends upon the Integrate: Ways to integrate applications both internally as well as externally and for that you need of course Inbound and Outbound API Management awareness or possibly Platforms. Reach New Customers: Excellent ways to reach new customers Implement New Business models: one in which API’s play center role of exchanging data Monetization: Pricing models – Spike arrests – Rate limiting – Throttling .wat nog meer? Evolving Product: believe it or not the Idea that API is piece of development that can be regarded as a 1-time action happens only too often. The idea that it is an Evolving Product is still often foreign.
- Creating and Deploying an API is just a one stage in its lifecycle. Sometimes there are breaking changes that require a restructuring of the API Response body. Or the Response output may no longer suffice the need of the receiver. The lifecycle of an API starts at the conception and design, centers during publication and ends with decommissioning. An API can be replaced with Versioning, become Superseded or immediately Decommissioned. API Providers are responsible for an organized and transparent transition to the latest API version (or endpoint) that is live and deprecate or decommission earlier versions of the API. Versioning can either be done through the URI or through a Header, please follow guidelines of the Guild. Make sure you are backward compatible.
- Roadmap: An easy and transparent way of aligning the organization what is coming next and making people more enthousiastic. My feeling is that nothing is more exciting than to know what API’s will be developed next and seeing people involved in that. Internal workshop and trainings: towards the rest of the organization. Highligthing the importance of API’s within their context. Always within their context because then it becomes more alive. Not some abstract Public API on the market but the ones their organization is developing. Accelerate B exec: with the right Go-to-market strategies, and a proper strategy around bringing an API onto the market it can accelerate your execution. Provide standardization: In the interactions, communications, responses, have standardized approach. The more reliable you are going to be in the end. Also within safeguarding the API Contracts with the Customers. And having a consistent Domain Terminology and really representing one side. So having agreed naming conventions for instance saves a lot of confusion. API Resources: Know what are the key tools, competences, areas of expertise that your organization needs and focus on them. I’ve been involved in hiring candidates and its not only the right experience that they accumulated but also a mindset of working in an integration field. Empower PO’s and Evangelist: you may not have an evangelist per se. But usually there is someone out there who follows the latest trends and spreads it. Product Owners are the bridge between the strategy and execution of API related work. Empower them with the freedom to follow up upon market developments. Constant Experimentation: Move away from the sense of being rather risk-averse and closed business culture to a culture of constant experimentation with stakeholders.
- Api Guild: best practices onto the table, discuss findings, reassess design decisions. Design First: You should be thinking about the entire lifecycle of an API. First share around the value and concept of the API, mock the API before you start implementing it. Saves you a lot of pain later on where certain design decisions cannot be reversed any more. Long Term: Plug & Play, Self-Service, Do it Yourself, Authentication & authorization, credentials giveouts. Quality Standards: Constant Guardianship: taking care of the API just as any other product, refactoring, versioning, updating documentation. Lipstick: Prevent business logic inside the API inteself, have the business logic reserved for the backend layer.
- Lack of API Culture: Consumer of APIs, become an extension of the API providers - for new applications and to new customers. They help these firms expand their businesses to places they couldn't otherwise reach. May require a lot of support. They can become very demanding – asking a lot from the API Developers. Centralize: often the maintainers of the Management and Developer Portals do that, but it doesn’t have to be that way. Customer orientation: can only be maintained if your actions don’t impede customization. Are you still flexible enough to jump into the next opportunity.