0
APIs are NOT SOA++
@edanuff
Ed Anuff

Dilshad Simons
groups.google.com/group/api-craft
youtube.com/apigee
slideshare.com/apigee
community.apigee.com
Agenda
•
•
•
•
•
CC-BY-SA

Recap
The A in API is for Apps
Top-down vs. Bottom-up
Getting there from here
What comes next
What we’ve said before
Separate SOA as an
architecture from specific
products
SOA is good practice
CC-BY-SA
Classic Differences
Self-service & lightweight
governance
External, fine-grained security
(OAuth)
Pace-layering
CC-BY-SA
Pace Layered Building

CC-BY-SA
This is SOA++
(sort of…)
CC-BY-SA
The A in API is for Apps
Rich Clients
(Visual Basic, Delphi, etc.)

Web Applications
(App Servers)

Rich Clients
(Mobile A...
App Servers
Emerged at the same time as
SOA
Monolithic presentation and
business logic
Hide deficiencies in SOA
architectu...
Client/Server/Service

HTTP

Browser
UI

CC-BY-SA

App Server
Page Templates
Business Logic

Services
Customers
Orders
Where do APIs fit in?
?
HTTP

API

Browser
UI

CC-BY-SA

App Server
Page Templates
Business Logic

Services
Customers
Orde...
Governance?
Scope of SOA Governance

HTTP

API

Browser
UI

CC-BY-SA

App Server
Page Templates
Business Logic

Services
C...
What about Apps?
Scope of SOA Governance

?
API

App
UI
Interaction Logic
Business Logic
CC-BY-SA

API

App Server
Service...
Apps Need API Tier
Scope of API Governance

API

App
UI
Interaction Logic
Business Logic
CC-BY-SA

Scope of SOA Governance...
Who builds the API Tier?
API Team?
App Team?
SOA Team?

CC-BY-SA
Who builds the API Tier?
API Team?
App Team?
SOA Team?

CC-BY-SA
Who builds the API Tier?
API Team?
App Team?
SOA Team?
All of the above
CC-BY-SA
What does API Tier do?
API exposure
- loosely coupled
App-specific consumption
- tightly coupled
CC-BY-SA
API Tier
App Consumption

API Exposure

• API adaptations needed for apps

• APIs architected for abstraction

• Enable de...
Evolving towards
API First
Monolithic Web App
Web
Apps

App
Server

Backend
Services

CC-BY-SA
API-adapted Web Apps

App
Server

Other
Apps

API

Web
Apps

Backend
Services

Consumption focused

CC-BY-SA
API-adapted SOA
Web
Apps

Other
Apps

ESB

API

App
Server

Exposure focused
Internal
Services

CC-BY-SA
API First
All Apps
Mobile
Apps

Web
Apps

Social
Apps

API Tier
Persistence

App
Servers
CC-BY-SA

Security

Orchestration...
What comes next?
API Mass Customization
App “A”

App “B”

App “C”

API “A”

API “B”

API “C”

API Tier
App
Servers

CC-BY-SA

ESB

Backend
...
API Tier Analytics
All Channels

Correlations
Cohorts

All Interactions

API Tier

Conversions
Segmentation
A/B & Multivar...
API Tier with Analytics
App Consumption
•
•
•
•

API Exposure

API adaptations needed for apps
Enable developers for busin...
to summarize…
APIs are not SOA++
APIs are built for both exposure and app-specific usage
APIs are a channel strategy as much or more so ...
@edanuff
Ed Anuff

Dilshad Simons

Questions?
community.apigee.com
Resources
Community:

http://community.apigee.com/

Webcasts: http://apigee.com/about/api-best-practices/all/webcast
eBook...
Thank you!
Upcoming SlideShare
Loading in...5
×

Why APIs are not SOA++

8,139

Published on

Published in: Technology, Business
0 Comments
23 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
8,139
On Slideshare
0
From Embeds
0
Number of Embeds
23
Actions
Shares
0
Downloads
300
Comments
0
Likes
23
Embeds 0
No embeds

No notes for slide
  • The idea behind pace-layering is that applications and the toolsets used for creating, managing and governing these apps depends on the need for business change, differentiation and innovation needs. Look at the pace of innovation of the platforms where apps are delivered to users. Innovation, differentiation, business value requires that enterprise app evolve at that pace. When it comes to backend systems stability, standardization and security are key. This essentially creates an impedance mismatch between the existing enterprise systems and the myriad of apps that consume them.
    The concept of pace layers as developed in a book titled, "How Buildings Learn” by Stewart Brand. He was addressing the challenge of designing a building that would have a long and useful life, be resilient to change, and be able to accommodate the needs of various owners and occupants. His technique was to identify a series of layers, ranging from the building site, which never changes, to the "stuff," such as chairs, lamps and pictures, that might move around on a daily or weekly basis. In between are layers, like the building structure, which could last 100 years; the skin or exterior surface, which might be redone every 20 years; and the services, such as plumbing; heating, ventilation and air-conditioning (HVAC) or electrical wiring, which are often replaced or updated in seven to 15 years. These architectural layers have very different paces of change, but they must be designed to work together for the building to function effectively. We believe this same idea of pace layers can be used to build a business application strategy that delivers a faster response and a better ROI, without sacrificing integration, integrity and/or governance.
  • E: So, things get interesting when we add mobile into the mix
    D: There are two APIs
    E: Right, this is where we get the revenge of client/server, we have an app talking over an API to an App Server and the App Server talking via an API to the rest of your services
    E: For a lot of enterprises, they have hundreds of these APIs on the left that they’re completely unaware of
    D: This is like the proliferation of Sharepoint
  • Transcript of "Why APIs are not SOA++"

    1. 1. APIs are NOT SOA++
    2. 2. @edanuff Ed Anuff Dilshad Simons
    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 • • • • • CC-BY-SA Recap The A in API is for Apps Top-down vs. Bottom-up Getting there from here What comes next
    8. 8. What we’ve said before Separate SOA as an architecture from specific products SOA is good practice CC-BY-SA
    9. 9. Classic Differences Self-service & lightweight governance External, fine-grained security (OAuth) Pace-layering CC-BY-SA
    10. 10. Pace Layered Building CC-BY-SA
    11. 11. This is SOA++ (sort of…) CC-BY-SA
    12. 12. The A in API is for Apps Rich Clients (Visual Basic, Delphi, etc.) Web Applications (App Servers) Rich Clients (Mobile Apps) CC-BY-SA
    13. 13. App Servers Emerged at the same time as SOA Monolithic presentation and business logic Hide deficiencies in SOA architectures CC-BY-SA
    14. 14. Client/Server/Service HTTP Browser UI CC-BY-SA App Server Page Templates Business Logic Services Customers Orders
    15. 15. Where do APIs fit in? ? HTTP API Browser UI CC-BY-SA App Server Page Templates Business Logic Services Customers Orders
    16. 16. Governance? Scope of SOA Governance HTTP API Browser UI CC-BY-SA App Server Page Templates Business Logic Services Customers Orders
    17. 17. What about Apps? Scope of SOA Governance ? API App UI Interaction Logic Business Logic CC-BY-SA API App Server Service Facades Business Logic Services Customers Orders
    18. 18. Apps Need API Tier Scope of API Governance API App UI Interaction Logic Business Logic CC-BY-SA Scope of SOA Governance API App Server Service Facades Business Logic App Server Service Facades Business Logic
    19. 19. Who builds the API Tier? API Team? App Team? SOA Team? CC-BY-SA
    20. 20. Who builds the API Tier? API Team? App Team? SOA Team? CC-BY-SA
    21. 21. Who builds the API Tier? API Team? App Team? SOA Team? All of the above CC-BY-SA
    22. 22. What does API Tier do? API exposure - loosely coupled App-specific consumption - tightly coupled CC-BY-SA
    23. 23. API Tier App Consumption API Exposure • API adaptations needed for apps • APIs architected for abstraction • Enable developers for business • Enable developers for API use • Security for app-to-API • Security for API-to-backend API App CC-BY-SA API App Server Services
    24. 24. Evolving towards API First
    25. 25. Monolithic Web App Web Apps App Server Backend Services CC-BY-SA
    26. 26. API-adapted Web Apps App Server Other Apps API Web Apps Backend Services Consumption focused CC-BY-SA
    27. 27. API-adapted SOA Web Apps Other Apps ESB API App Server Exposure focused Internal Services CC-BY-SA
    28. 28. API First All Apps Mobile Apps Web Apps Social Apps API Tier Persistence App Servers CC-BY-SA Security Orchestration ESB Analytics Backend Services
    29. 29. What comes next?
    30. 30. API Mass Customization App “A” App “B” App “C” API “A” API “B” API “C” API Tier App Servers CC-BY-SA ESB Backend Services
    31. 31. API Tier Analytics All Channels Correlations Cohorts All Interactions API Tier Conversions Segmentation A/B & Multivariate Analytics All Backends CC-BY-SA
    32. 32. API Tier with Analytics App Consumption • • • • API Exposure 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 Analytics API App CC-BY-SA API App Server Services
    33. 33. to summarize…
    34. 34. APIs are not SOA++ APIs are built for both exposure and app-specific usage APIs are a channel strategy as much or more so than an integration strategy Web-tier is now built against the same set of APIs as the mobile tier All interactions across mobile, web, social, and partners are observable API Tier is the last stop before mobile CC-BY-SA
    35. 35. @edanuff Ed Anuff Dilshad Simons Questions?
    36. 36. community.apigee.com
    37. 37. 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
    38. 38. Thank you!
    1. A particular slide catching your eye?

      Clipping is a handy way to collect important slides you want to go back to later.

    ×