apis inside enterprise - soa displacement?

APIs Inside the Enterprise

Dino Chiesa@dpchiesa

Apigee@apigee

Greg Brail@gbrail

SOA Displacement?

groups.google.com/group/api-craft

youtube.com/apigee

slideshare.net/apigee

Dino Chiesa@dpchiesa

@apigee

Greg Brail@gbrail

In the beginning….

Data

Application

Xerox 820 CP/M Machine

Proliferation

ApplicationData

CRM

DataERP

Data Risk

Application

Applications Become Services

Service interface

Data

Service implementation

SOAP, JMS, XML…

Services in the Network

Controlled Interconnection and Re-use

Data

CRM

DataERP

Data Risk

A Service Bus

Data

CRM

DataERP

Data Risk

The Service or Message Bus

OSS

Other Corporate

SVs

BSS

EnterpriseOrchestration

BPM

BRMS

Application

REMOTE DATA CENTERDeployment Option C

REMOTE DATA CENTERDeployment Option B

REMOTE DATA

CENTERDeployment

Option A

Application

Application

Application

ApplicationOrchestration

BPM

BRMS

DOMAIN ESB

Platform

Application

Application

ApplicationOrchestration

BPM

BRMS

DOMAIN ESB

Platform

Application

ExternalMashups

ExternalMashups

Hosted Services(e.g., google,

facebook)

BPM

BRMSJava

Service DeliveryOrchestration

Identity & AccessManagement(Common)

MAIN ESB – A

API Gateway Internal Mashups(e.g., web 2.0)

ESB Gateway

InvocationModule

APIDirectory

ExternalUsers

MAIN ESB – B MAIN ESB – CORPORATE SVCs

Big Data

Profile DB

Service Events Mgmt,Processing & Continuous

IntelligenceOther

Modules

We’ve All Been Here

Changing Constraints

2005: Yahoo Maps API

2005: Flickr API

2007: First iPhone & SDK

Service Orientation? Meet the Smartphone

?

SOAStrict contractsBasic ConnectivityFew, known developers,

Strictly managedSlow, unreliable,

segmented networks

APIsLoose contractsMinimal “stack”Self-service1000s of developersO(10^4) users, externalAlways connected apps

Different Sets of Requirements

Changes in Technology

Why OAuth and not WS-Security?

Why JSON and not XML?

Why the focus on HTTP?

Why add Developer on-boarding?

Why add Analytics?

The metaphor gets us to think differently.

Rapid iteration

Programmability from anything

Loose documentation

YAGNI

APIs as Design Metaphor

“Software is eating the world”

Credit: http://goo.gl/QzvX8

APIs as a Façade for SOA and ESB

Change your DNA

Questions?

THANK YOUSubscribe to API webcasts at:

youtube.com/apigee

THANK YOUQuestions and ideas to:

groups.google.com/group/api-craft

THANK YOU@dpchiesa@gbrail

@apigee