Downloaded 91 times
Uploaded byApigee | Google Cloud
API First: Going Beyond SOA, ESBs, and Integration
1. APIs allow applications to access resources and services in a standardized way, enabling app-to-app communication. APIs have become the preferred way for applications to integrate both internally and externally developed services rather than older integration approaches like ESBs. 2. Microservices architecture breaks applications into small, independent services that communicate through APIs. This allows individual services to be developed and scaled independently. 3. The document outlines an evolution from monolithic applications to API-first architectures, where APIs are designed for external use from the start rather than being added later. In this model, APIs provide access to all internal and external resources and analytics can be applied at the API layer.
More Related Content
Similar to API First: Going Beyond SOA, ESBs, and Integration
API First: Going Beyond SOA, ESBs, and Integration
- 1. 1 API-First: Going BeyondSOA, ESB, and Integration Ed Anuff, Apigee Brian Pagano, Apigee
- 2.
- 3. What do wemean by APIs?
- 4. The A inAPI is for apps Rich clients (Visual Basic, Delphi, etc.) Thin clients (Web Applications) Rich clients (Mobile Apps)
- 5.
- 6.
- 7.
- 8. Modern server-side app •Oftenruns in an app server •Monolithic presentation and business logic •Hosted in an environment (often a virtualized container) •Increasingly lightweight
- 9.
- 10. Apps need resources •Databasesand storage •Email services •Sometimes integration-based, but increasingly API-based
- 11. APIs are notSOA++
- 12. Cloud business services •Database-as-a-Service •Storage-as-a-Service •Email-as-a-Service •MQ-as-a-Service •Allare already in widespread use …
- 13. Internal resources •Many newresource 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 applicationlogic & infrastructure
- 15. Sometimes apps talkto other apps
- 16. API Front end BackendAPI App APIAPIAppApp Internal External
- 17. App-to-app •API-centric: app developersexpose their own APIs and learns others’ APIs •Integration: normalized data interchange •Agility trade-off
- 18.
- 19. Okay, we haveto talk about microservices
- 20. Internal API Front end BackendAPI APIAPI AppApp ServiceService 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
- 22.
- 23. Monolithic web app Webapps App server Backend services
- 24. API-adapted Web Apps Consumption-focused WebApps App Server Backend Services Other apps API
- 25. API-adapted SOA Exposure-focused Web apps Appserver Internal services Other apps API ESB
- 26. API-first enterprise Web apps Appservers Backend services ESB Mobile apps API tier All apps Security AnalyticsPersistence Orchestration Other apps
- 27.
- 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 Allchannels API Tier All backends All interactions Analytics Correlations Cohorts Conversions Segmentation A/B & multivariate
- 30. API tier withanalytics • 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 forApps •APIs are not SOA++ •Microservices? •How to get to an API-centric architecture
Editor's Notes
- #15 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.