APIs != Integration

The Presentation inside:

Slide 0

APIs != Integration

Slide 1

Ed Anuff @edanuff Brian Pagano @brianpagano

Slide 2


Slide 3


Slide 4


Slide 5


Slide 6

Agenda What is integration? The A in API is for apps All development is API development CC-BY-SA

Slide 7

Why? The app developer is king The right tool for the job CC-BY-SA

Slide 8

What is Integration? Typically backend-to-backend, sometimes application to application Often connector-based MQ, ESB, EAI, ORBs CC-BY-SA

Slide 9

The A in API is for Apps Rich clients (Visual Basic, Delphi, etc.) Web applications (app servers) Rich clients (mobile apps) CC-BY-SA

Slide 10


Slide 11

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

Slide 12

App Backend CC-BY-SA API

Slide 13

Apps Need Resources Databases and storage Email services Sometimes integration-based, but increasingly API-based CC-BY-SA

Slide 14

12-Factor Apps MIT License Adam Wiggins http://12factor.net/ IV. Backing Services Treat backing services as attached resources

Slide 15

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

Slide 16

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

Slide 17

App Front end Backend CC-BY-SA App Backend CC-BY-SA API API

Slide 18

App code SDK Mobile API Architecture CC-BY-SA

Slide 19

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

Slide 20

App Front end Backend App App CC-BY-SA API API API API

Slide 21

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

Slide 22

Front end Backend App App Service Service Service Service Service Service Micro service architecture APIs APIs CC-BY-SA API API API API

Slide 23

Micro-Services Components are services, not in-process objects Allows polyglot programming Easier to scale component services individually CC-BY-SA

Slide 24

to summarize…

Slide 25

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

Slide 26

Questions? Ed Anuff @edanuff Brian Pagano @brianpagano

Slide 27


Slide 28

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

Slide 29

Thank you!