API First: Going Beyond SOA, ESBs, and Integration
•Télécharger en tant que PPTX, PDF•
2 j'aime•1,394 vues
Going Beyond SOA, ESBs, and Integration at I Love APIs 2015
Recommandé
Recommandé
Contenu connexe
Tendances
Tendances (20)
Similaire à API First: Going Beyond SOA, ESBs, and Integration
Similaire à API First: Going Beyond SOA, ESBs, and Integration (20)
Plus de Apigee | Google Cloud
Plus de Apigee | Google Cloud (20)
Dernier
Dernier (20)
API First: Going Beyond SOA, ESBs, and Integration
- 1. 1 API-First: Going Beyond SOA, ESB, and Integration Ed Anuff, Apigee Brian Pagano, Apigee
- 3. What do we mean by APIs?
- 4. The A in API is for apps Rich clients (Visual Basic, Delphi, etc.) Thin clients (Web Applications) Rich clients (Mobile Apps)
- 5. App
- 7. App
- 8. Modern server-side app •Often runs in an app server •Monolithic presentation and business logic •Hosted in an environment (often a virtualized container) •Increasingly lightweight
- 10. Apps need resources •Databases and storage •Email services •Sometimes integration-based, but increasingly API-based
- 11. APIs are not SOA++
- 12. Cloud business services •Database-as-a-Service •Storage-as-a-Service •Email-as-a-Service •MQ-as-a-Service •All are already in widespread use …
- 13. Internal resources •Many new resource services already are API-based •Developers prefer to use APIs even with the added work of learning APIs versus ESB approaches
- 14. SDK API Mobile API architecture CC-BY-SA Device-side app logic Server-side application logic & infrastructure
- 15. Sometimes apps talk to other apps
- 16. API Front end BackendAPI App APIAPI AppApp Internal External
- 17. App-to-app •API-centric: app developers expose their own APIs and learns others’ APIs •Integration: normalized data interchange •Agility trade-off
- 19. Okay, we have to talk about microservices
- 20. Internal API Front end BackendAPI APIAPI AppApp Service Service Service Service Service Service Service Service Service APIs APIs Microservice architecture External
- 21. Microservices •Components are services, not in-process objects •Allows polyglot programming •Easier to scale component services individually
- 23. Monolithic web app Web apps App server Backend services
- 24. API-adapted Web Apps Consumption-focused Web Apps App Server Backend Services Other apps API
- 25. API-adapted SOA Exposure-focused Web apps App server Internal services Other apps API ESB
- 26. API-first enterprise Web apps App servers Backend services ESB Mobile apps API tier All apps Security AnalyticsPersistence Orchestration Other apps
- 27. What comes next?
- 28. API mass customization App “B” App servers Backend services ESB App “A” API Tter App “C” API “B”API “A” API “C”
- 29. API tier analytics All channels API Tier All backends All interactions Analytics Correlations Cohorts Conversions Segmentation A/B & multivariate
- 30. API tier with analytics • API adaptations needed for apps • Enable developers for business • Security for app-to-API • App and behavior analytics • APIs architected for abstraction • Enable developers for API use • Security for API-to-backend • API analytics APIAPI App consumption API exposure App server ServicesApp Analytics
- 31. Summary •“A” is for Apps •APIs are not SOA++ •Microservices? •How to get to an API-centric architecture
Notes de l'éditeur
- By using a lightweight library you can use API calls to Create, Read, Update, and Delete data with ease. The backend manages access and security through it’s API, and the server infrastructure make’s sure your data is backed up and safe.