cloud principles

Cloud Principles

FrontendBuild To Change


ServicesDesign To Last






AmazonAmazon

GoogleGoogle

SalesForceSalesForce

ERPERP billingbilling

Cloud integration mechanisms

Decoupled

Store-front

Inside-Out

Decoupled: Force.com

Force.comForce.com

SFASFA HRMHRM KMSKMS CustomCustom

ForceSitesForceSites

SAP initiates import and export of data. Orders in force.com are unresolved and new customers will be leads until a successful feedback of the backend is given.This mechanism is called decoupled and requires not much changes on the current IT landscape.

SAPSAP

ForceSitesForceSitesForceSitesForceSites

11

22

33

Independent development of steps is possible:1.Front-end User Interface (starting with leads)2.Loading of customer data from your backend

3.Getting contracted updates and changes to your backend

Decoupled

• Can be implemented without backend where updates are managed manually

• Strong separation of concern• Only keep parts highly available for the

Internet and not for internal use (no costs)• No problems in maintenance and update

schedules• Mandates an asynchronous application

design.

Storefront using AWSBusiness

Build For ChangeBusiness

Build For ChangeProcessBuild To LastProcessBuild To Last

CMSCMS

User (Browser)User (Browser)

HR CRM sales DB

Process Layer

Online Integration (I/O)Online Integration (I/O)

staticstatic datadata

CDNCDN BASICBASIC

CustomerData

ContentData

SiteLogic

Storefront

• Enhances the companies webpresence by placing this in the cloud

• Physical separation of concern• Very fast and scalable for content• Technology independent because integration

is in the frontend

Example Inside-Out:

Google- Extends current application infrastructure- Keeps secure data out of the cloud- High performance infrastructure needed which can be placed in a (private) cloud-Extends existing service oriented mechanisms

Can also be used in other scenario’s as extension for the internal infrastructure.

Inside Out

• Use cloud resources when needed from inside:– Cloudbursting (hadoop)– Surge computing (cpu on demand)– Enterprise Application Webservices

• For (more) mature IT environments• Scaling up performance, scale back IT

What to use?

InboundlogisticsInboundlogistics

OperationsOperations

OutboundLogisticsOutboundLogistics

Marketing& Sales

Marketing& Sales

ServiceService

Inside-OutInside-Out DecoupledDecoupled Store-frontStore-front

Sample of an basic architecture based on Porter’s Value Chain

Let’s take Porter’s value chain as a basis………

Migration Tactics

• Slow adoption strategyUse a small feature basis and roll-out new ones weekly instead of big bang

• Use intermediate data formatsMigration data always in independent formats for rollback/alternative scenario

• Plan company data backup (retention)• Network and infrastructure planning

Since network connectivity is key for cloud