Embed Size (px)
DESCRIPTION
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
Citation preview
APIs != Integration
Ed Anuff@edanuff
Brian Pagano@brianpagano
groups.google.com/group/api-craft
youtube.com/apigee
slideshare.com/apigee
community.apigee.com
Agenda
• What is integration?• The A in API is for apps• All development is API
development
CC-BY-SA
Why?
• The app developer is king
• The right tool for the job
CC-BY-SA
What is Integration?
Typically backend-to-backend, sometimes application to application
Often connector-based
MQ, ESB, EAI, ORBs
CC-BY-SA
The A in API is for Apps
Rich clients(Visual Basic, Delphi, etc.)
Web applications(app servers)
Rich clients(mobile apps)
CC-BY-SA
App
CC-BY-SA
Modern Server-side App• Often runs in an app server
• Monolithic presentation and business logic
• Hosted in an environment (often a virtualized container)
• Increasingly lightweightCC-BY-SA
App
Backend
CC-BY-SA
API
Apps Need Resources
• Databases and storage
• Email services
• Sometimes integration-based, but increasingly API-based
CC-BY-SA
12-Factor Apps
MIT License
Adam Wiggins http://12factor.net/
IV. Backing ServicesTreat backing services as attached resources
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
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
App
Front end
Backend
CC-BY-SA
App
Backend
CC-BY-SA
API
API
Appcode
SDKServer
infrastructureAPI
Mobile API Architecture
CC-BY-SA
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
App
Front end
Backend
AppApp
CC-BY-SA
API
API
APIAPI
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
Front end
Backend
AppAppServi
ceServi
ceServi
ce
Service
Service
Service
Service
Service
Service
Micro service architecture
CC-BY-SA
APIAPI
API
API
Micro-Services
Components are services, not in-process objects
Allows polyglot programming
Easier to scale component services individually
CC-BY-SA
to summarize…
APIs != IntegrationAPIs 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
Questions?
Ed Anuff@edanuff
Brian Pagano@brianpagano
community.apigee.com
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
Thank you!
