Why APIs are Different Than Integration


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 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.

- 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

Why APIs are Different Than Integration

  1. 1. APIs != Integration
  2. 2. Ed Anuff @edanuff Brian Pagano @brianpagano
  3. 3. groups.google.com/group/api-craft
  4. 4. youtube.com/apigee
  5. 5. slideshare.com/apigee
  6. 6. community.apigee.com
  7. 7. Agenda • What is integration? • The A in API is for apps • All development is API development CC-BY-SA
  8. 8. Why? • The app developer is king • The right tool for the job CC-BY-SA
  9. 9. What is Integration? Typically backend-to-backend, sometimes application to application Often connector-based MQ, ESB, EAI, ORBs CC-BY-SA
  10. 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. 11. App CC-BY-SA
  12. 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. 13. App Backend CC-BY-SA API
  14. 14. Apps Need Resources • Databases and storage • Email services • Sometimes integration- based, but increasingly API- based CC-BY-SA
  15. 15. 12-Factor Apps MIT License Adam Wiggins http://12factor.net/ IV. Backing Services Treat backing services as attached resources
  16. 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. 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. 18. App Front end Backend CC-BY-SA App Backend CC-BY-SA API API
  19. 19. App code SDK Server infrastructure API Mobile API Architecture CC-BY-SA
  20. 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. 21. App Front end Backend AppApp CC-BY-SA API API APIAPI
  22. 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. 23. Front end Backend AppApp Service Service Service Service Service Service Service Service Service Micro service architecture CC-BY-SA APIAPI API API
  24. 24. Micro-Services Components are services, not in-process objects Allows polyglot programming Easier to scale component services individually CC-BY-SA
  25. 25. to summarize…
  26. 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. 27. Questions? Ed Anuff @edanuff Brian Pagano @brianpagano
  28. 28. community.apigee.com
  29. 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. 30. Thank you!