apidays LIVE London 2021 - Moving from a Product as API to API as a Product by Francois Lasne, Finastra
0 likes•140 views
The document outlines the transition from viewing APIs as mere add-ons to recognizing them as essential products in the evolving financial landscape. It emphasizes the need for a mindset shift in API development, focusing on design, business integration, and user experience to foster innovation and ensure competitive advantage. The author highlights Finastra's commitment to this transformation through community engagement, conference participation, and a structured approach to API governance.
apidays LIVE London 2021 - Moving from a Product as API to API as a Product by Francois Lasne, Finastra
- 1. From “product has API” to “API as a product” The API journey
- 2. Francois LASNE Director Open API FusionFabric.cloud Finastra Member of #PSD2 Member of 80+ companies workshop owner about API governance #OpenBanking
- 3. From “product has API” to “API as a product” The Open API journey
- 4. New York JULY Australia SEPTEMBER Singapore APRIL Helsinki & North MARCH Paris DECEMBER London OCTOBER Jakarta FEBRUARY Hong Kong AUGUST JUNE India MAY Check out our API Conferences here 50+ events since 2012, 14 countries, 2,000+ speakers, 50,000+ attendees, 300k+ online community Want to talk at one of our conferences? Apply to speak here
- 5. From a product , to a service , to a solution This is a Product This is a solution An ecosystem This is a Service
- 6. This is the new reality of Finance only France : 735+ fintech (source Bpi) You are Nothing … … without the others
- 7. From “product has API” to “API as a product” It’s a change of mind set Product Then To Product Then Because of What are you doing best ? things at the beginning or at the end API 1st Or Mock Mocking, BDD, consistency Feedback loop
- 8. From But I have already API ? Can I publish them as Open API ? Do not expose your complexity , Hide the dinosaur, reduce technical dept It is a modernization journey , Learn from the past, built the future Simple is beautiful Why ? API design Mocking, BDD, consistency Design / (re) Design first approach
- 9. From “product has API” to “API as a product” Swagger Open API specification 3.0 Json HTTP (verbs , header ) Implementation (java , Node et Is it a technical beast ? • Developer portal • API Gateway • Self Registration • Security policy (Application registration , Oauth2 , API key etc. ) • Monitoring platform • Billing platform • Pipeline of publication to ensure good API (stay tuned ! Will do a specific presentation Paris ) Tooling Specification
- 10. From “product has API” to “API as a product” Design together (business analyst & architect) # no silo Specification is a technical artefact for a Business interface An agreement, a contract Business to Business Business to Consumer Partnership Understand what market demands Connect It’s about Business too
- 11. Roles of an API program manager API connect products, and people Partner enablement Sales Marketing Legal HR Security Technology / implementation Technical Architecture Product roadmap and vision Business Architect Documentation Operation Support Consistent BE an API man
- 12. Initiate ▪ Business Definition ▪ Feasibility ▪ Prioritization Define ▪ Interface definition ▪ KPI definition ▪ Validation Develop ▪ Coding ▪ Deploying on Dev env ▪ Testing ▪ Security Integrate ▪ Perf testing ▪ Security testing ▪ Data privacy ▪ Pricing review ▪ Marketing review ▪ Transition to Operation Production ▪ Publication to production ▪ Alert and monitoring ▪ Support ▪ Telemetry ▪ Billing Open API @ Finastra, API as a Product The open API journey Feedback loop
- 13. API 1st Journey Culture eats Strategy for Breakfast
- 14. From “product has API” to “API as a product” The Open API journey One more Thing …
- 15. One more Things … From “product has API” to “API as a product” • You have a digital experience with your client • You Should Provide Self Service , Sandboxing, and testable – No Test no way ! • You work in a competitive world ! – Often your client will test 2 or 3 service providers, it is so easy ! • Your Documentation need to be perfect, Self explainable, self service – I do not understand , Next …. • Change is very costly – You can change Gmail UI or product , not gmail API • Multiple usage of API – You do not know how your client will use it => foster innovation , organize Hackathon ! Networking API is public
- 16. API as a Product It’s a transformation journey An exciting one !
- 17. API 1st Product Mock Then Mock so that review, so that feedback , Behavior Driven Development, Product Then How many of you have sequence diagram documented
- 18. API as a product Versioning , breaking changes , need more stability ,life cycle Everything becomes public B2B / B2C , Quality specific tooling and pipeline , Training and skills Testing , compliance , Silo API is not technical is functional API is technical also … implementation / implantability Integration partner / public / employee are my customer
- 23. New York JULY Australia SEPTEMBER Singapore APRIL Helsinki & North MARCH Paris DECEMBER London OCTOBER Jakarta FEBRUARY Hong Kong AUGUST JUNE India MAY Check out our API Conferences here 50+ events since 2012, 14 countries, 2,000+ speakers, 50,000+ attendees, 300k+ online community Want to talk at one of our conferences? Apply to speak here