Your SlideShare is downloading. ×
Why APIs are Different Than Integration
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Why APIs are Different Than Integration

2,864

Published on

IT architects and developers have long recognized APIs as an evolution and continuation of integration-based architectures used within enterprise IT. But this is a limited view. APIs have become the …

IT architects and developers have long recognized APIs as an evolution and continuation of integration-based architectures used within enterprise IT. But this is a limited view. APIs have become the foundational framework for development of scalable enterprise applications that connect user experiences to back-end data and services.

How will this API-centric architecture play a role in your application systems and in your business? Join Ed Anuff and Brian Pagano as they discuss the many important implications of API-centric architecture.

Learn:
- the characteristics of an API-centric architecture
- how APIs are influencing front-end, back-end, and app-to-app systems
- how APIs change the way data is leveraged
- why traditional architecture cannot address new business challenges

Published in: Engineering, Technology, Business
1 Comment
15 Likes
Statistics
Notes
No Downloads
Views
Total Views
2,864
On Slideshare
0
From Embeds
0
Number of Embeds
12
Actions
Shares
0
Downloads
172
Comments
1
Likes
15
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. APIs != Integration
  • 2. Ed Anuff @edanuff Brian Pagano @brianpagano
  • 3. groups.google.com/group/api-craft
  • 4. youtube.com/apigee
  • 5. slideshare.com/apigee
  • 6. community.apigee.com
  • 7. Agenda • What is integration? • The A in API is for apps • All development is API development CC-BY-SA
  • 8. Why? • The app developer is king • The right tool for the job CC-BY-SA
  • 9. What is Integration? Typically backend-to-backend, sometimes application to application Often connector-based MQ, ESB, EAI, ORBs CC-BY-SA
  • 10. The A in API is for Apps Rich clients (Visual Basic, Delphi, etc.) Web applications (app servers) Rich clients (mobile apps) CC-BY-SA
  • 11. App CC-BY-SA
  • 12. 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 CC-BY-SA
  • 13. App Backend CC-BY-SA API
  • 14. Apps Need Resources • Databases and storage • Email services • Sometimes integration- based, but increasingly API- based CC-BY-SA
  • 15. 12-Factor Apps MIT License Adam Wiggins http://12factor.net/ IV. Backing Services Treat backing services as attached resources
  • 16. 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… CC-BY-SA
  • 17. 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 CC-BY-SA
  • 18. App Front end Backend CC-BY-SA App Backend CC-BY-SA API API
  • 19. App code SDK Server infrastructure API Mobile API Architecture CC-BY-SA
  • 20. Clients Mobile clients talking to server-side apps via an API • TIGHTLY-COUPLED •NOT INTEGRATION, NOT SOA HTML5/JS and single page apps CC-BY-SA
  • 21. App Front end Backend AppApp CC-BY-SA API API APIAPI
  • 22. App-to-App API-centric: app developers expose their own APIs and learns others’ APIs Integration: normalized data interchange Agility trade-off CC-BY-SA
  • 23. Front end Backend AppApp Service Service Service Service Service Service Service Service Service Micro service architecture CC-BY-SA APIAPI API API
  • 24. Micro-Services Components are services, not in-process objects Allows polyglot programming Easier to scale component services individually CC-BY-SA
  • 25. to summarize…
  • 26. APIs != Integration APIs are used for both integration and non-integration use- cases APIs are used to facilitate communications to the backend APIs enable powering engagement at the front-end APIs connect applications to applications App components are being built as micro-services CC-BY-SA
  • 27. Questions? Ed Anuff @edanuff Brian Pagano @brianpagano
  • 28. community.apigee.com
  • 29. Resources Community: http://community.apigee.com/ Webcasts: http://apigee.com/about/api-best-practices/all/webcast eBooks: http://apigee.com/about/api-best-practices/all/ebook Institute: http://pages.apigee.com/institute.html Learn: http://community.apigee.com/learn I Love APIs: http://apigee.com/about/iloveapis-conference
  • 30. Thank you!

×