crossing the firewall integrating cloud computing into the enterprise ken yagen senior director,...

18
Crossing the Firewall integrating Cloud Computing into the enterprise Ken Yagen Senior Director, MuleSource [email protected] www.twitter.com/kenyagen

Post on 22-Dec-2015

214 views

Category:

Documents


0 download

TRANSCRIPT

Crossing the Firewallintegrating Cloud Computing into the enterprise

Ken YagenSenior Director, [email protected]/kenyagen

Evolution of Architecture

1960s 1970s 1980s 1990s 2000sTim e

Serviceorientation

Com ponent-baseddevelopm ent

O bjectorientation

Subroutinesand functions

M ultip lejobs

Decom positionapproaches

Enterprise ITdecom position

Applicationsdecom position

R osen, M ichae l. App lied SO A

Cloud Computing

CallCenter

Legacy

CRM Finance HRMS

Mess-aging / Collab-oration

SOA / SAAS

CallCenter CRM Finance HRMS

Mess-aging / Collab-oration

Schedul-ing

CallRouting

IVR

AR/AP

Fulfill-ment

Billing

Enterprise Service Bus

Cloud Computing

Reusable cloud-based services

Application as a Service

Platform as a Service

Infrastructure as a Service

Existing investments?

CONTROL

Cloud-ilities?Weaknesses Strengths

Scalability

Elasticity

Time to market

Security

Reliability

Manageability

New Applications

Schedul-ing

CallRouting

IVR

AR/AP

Fulfill-ment

Billing

Enterprise Service Bus

CRM

New Applications

Schedul-ing

CallRouting

IVR

AR/AP

Fulfill-ment

Billing CRM

Enterprise Service Bus

App

Virtualized Services

Schedul-ing

CallRouting

IVR

AR/AP

Fulfill-ment

Billing CRM

Enterprise Service Bus

App

CRMCallRtg

Scheduling

Billing

EmailHiring

AppApp

App

Enterprise Service Bus

How do I get here?

Checklist

connect the dotswith Mule

Reuse existing skills

> mvn mule-project-archetype:create \ -DartifactId=inventory \ -DmuleVersion=2.1.2

<service name="crmServiceProxy"> <inbound> <jms:inbound-endpoint queue="leads.queue"/> <forwarding-router/> </inbound> <outbound> <chaining-router> <http:outbound-endpoint address=“http://www.mycrm.net”/> </chaining-router> </outbound></service>