apidays LIVE Paris 2021 - Scale up your business with API integration by Mathieu Rasse, Meta API
•Download as PPTX, PDF•
0 likes•26 views
apidays LIVE Paris 2021 - APIs and the Future of Software December 7, 8 & 9, 2021 Scale up your business with API integration Mathieu Rasse, CEO at Meta API
Recommended
Recommended
More Related Content
Similar to apidays LIVE Paris 2021 - Scale up your business with API integration by Mathieu Rasse, Meta API
Similar to apidays LIVE Paris 2021 - Scale up your business with API integration by Mathieu Rasse, Meta API (20)
More from apidays
More from apidays (20)
Recently uploaded
Recently uploaded (20)
apidays LIVE Paris 2021 - Scale up your business with API integration by Mathieu Rasse, Meta API
- 1. Scale up your business with API integration
- 2. Author 2013 - IT expert @SUPINFO 2013 - Head of R&D @Dubbing Brothers 2017 - Lead Developer @Kumullus 2021 - CEO @Meta-API API Expert - CEO of Meta API
- 3. Summary ● The need of external services ● Common use cases ● The challenge of API integration ● Maintain agility with time ● Demo of Meta API
- 4. The need of external services - business side Simplify workflows Save time on repetitive / manual tasks Aggregate data to take more informed decisions
- 5. The need of external services - tech side Speed up your time- to-market Free your dev team from complex features ● Engage your responsibilities for an uncontrolled service ● Can be costly at scale BUT
- 6. Common use cases Payment Transactional emails Collaborative files storage Communication
- 7. The challenge of API integration Searching for the best candidate : - A service provider that will fulfill all requirements - An API covering all the features - An accessible and interactive documentation - Bonus : an SDK made for your programming language Checklist before choosing a service : - Check both your services features and API - Have a look to the documentation
- 8. The challenge of API integration Some tricky parts for your API integration: Authentication (OAuth 2) Rate limiting Excessive pagination
- 9. Maintain agility with time An integration is not a setup work: it implies maintaining with time External factors: - New features and deprecated endpoints - Price can change - Technical adjustment on APIs Internal factor: - Business process can increase or change usage - Your product may need a different tool
- 10. Maintain agility with time An abstraction layer for making everything easier Your business logic, ORM, main processes... An abstraction layer with: - Your configuration - Auth, API Keys... - Requests to API - Data transformation Your application External services
- 11. We combine everything inside a platform: Meta-API Handling the whole process from integration to maintenance Spell development with dev environment Use of Connectors Pick public APIs or create your private ones Release to production create a production version, auto- scalable Automatic monitoring Customized notifications are sent in case of an error Continuous improvement Add new features, change APIs, update your business logic 11 Explore & Develop Test, deploy and monitor Maintain & improve
- 12. Demo
Editor's Notes
- Simplify workflow : For team efficiency Save time on repetitive / manual tasks: focus on more strategic tasks/ other projects Aggregate data to take more informed decisions: Agility for your teams and
- Speed up your time-to-market : Very competitive market and environment, so speed can be a game changer An easy way to quickly prototype new features before create a more customized or homemade version, at a low price Free your dev team from complex features : Some “simple” features can be very hard to build or may require an extensive infrastructure Like the argument for the time to market : create a quick prototype --- Cons : Responsibilities : In case of a downtime on a critical process -> impact your own SLA Time to recover can be uncontrolled Cost : Many services have a pay-on-demand plans: cheap to start but costly with high volumes. Dangerous if your business model is not indexed to these costs.
- All these examples are popular because based on complex and costly infrastructure Some services are also only accessible through business services providers
- API covering all the feature : Starting with the interface and then use the API once your businesses processes are clarified. Ex : accounting An accessible and interactive documentation : Stripe is one of the best example Bonus : a library made for your programming language : Big actors release and maintain libraries on multiple languages (PHP, Ruby, NodeJS) You can rely sometimes on community packages if this service is popular enough (check Github)
- Authentication : OAuth 2 is complex because it imply to expose a public route for the server’s provider Rate limiting : Some lib can help you (for example, bottleneck on NodeJS) Be careful of loops Pagination : Will need some specifics loops on your code if you plan to retrieve many items Check the API docs : you can maximize the number of elements you can retrieve at once Some SDK can manage pagination for you Be careful of rate limiting also
- New features and deprecated endpoints Happen most when migration to a new API version (v1 to v2). Most of the time, actors let months to consumer to update their integrations. Pricing can change : Reference to Google Maps dumping (2018) Technical adjustment on APIs : Micro changes, like how pagination work or default sorted elements, that can need some minor adjustments