© 2010 VMware Inc. All rights reserved

Confidential

7 Best Practice when moving to Enterprise PaaS

2 Confidential

How do I start?

How do I Start?

I would like a PaaS but how?

Other people must have do this before?

How do I avoid the common pitfalls?

3 Confidential

Our Story

Our Story

We travel the world helping enterprises adopt PaaS

Every enterprise is unique however there are common requirements

Lets talk about a common set of best practices when considering adopting PaaS

4

Enterprise PaaS – 7 Best Practices

1. Discover

2. Modernize

3. Define

4. Adopt

5. Monitor

6. Scale

7. Integrate

5

The Current State

Discover

6

The Current StateDiscover

People System

Projects Requirements

7

Application Discovery Discover

Application Discovery

Use tools to investigate what applications are running within YOUR enterprise

Understand the dependency between applications

Build relationships with application owners and understand lifecycle

8

Application Classification Discover

“Cloud Ready” Modernize Middleware

Modernize Code Base Immovable Object

9

Application Modernization

Modernize

10

Cloud Ready

Cloud Ready

Identify development teams ready to adopt cloud

The application should operate in an elastic environment

Uses lightweight and lean middleware

Modernize

11

Modernize Middleware

Modernize Middleware

Existing middleware impacts agility by tightly coupling applications to underlying application server and other middleware components

Move to modern elastic middleware

Many modern application have already adopted frameworks.

Modernize

12

Modernize Code Base

Modernize Code Base

Develop using modern frameworks agile apps decoupled from middleware

Frameworks can improve developer productivity and innovation by 50%

Frameworks separate the application from the underlying middleware

Modernize

13

Immovable Object

Immovable Object

There will be application that can’t be redeveloped or migrated to an elastic application platform

Look at integration strategies that allow you to bridge the gap.

Modernize

14

Target State

Define

15

Goal of Platform as a Service (PaaS)

Friction-free deployment

No machines or middleware to manage

Latest high productivity frameworks

Choice of application services

Cloud portability

More responsive to developers

Elastic and dynamically scalable

Improved efficiency

Digest future cloud advances

Cloud portability

Application Developers

“Write code, not tickets”

IT Operations

“IT as a service provider”

Boost application

velocity

16

Clou

d Pr

ovid

er In

terfa

ce

Application Service Interface

Private Clouds

PublicClouds

Micro

Clouds

Reference Architecture

.js

Data Services

Other Services

Msg Services

.COM

…

Define

17

Reference Architecture Demonstration

17

18

Your Roadmap

Define Your Roadmap

Plan YOUR journey in YOUR timelines

Evolve YOUR business and IT at your pace

Define clear and achievable milestones

Define

19

Platform Adoption

Adopt

20

Your Journey

Your Journey

Start early in the application cycle:

Building application for the cloud

Cloud first policy for new applications

Cloud based application development

Champion teams

Adopt

21

PaaS DevelopmentDemonstration

22

Platform Monitoring

Monitor

23

Monitoring

Monitoring

PaaS is providing an application platform which requires a new way of looking at monitoring.

Monitor for application failures

Identity application load trends

Stop application layer bottlenecks

Monitor

24

Deep Performance Insight into Spring Apps Spring Insight Enterprise

Description Benefits

• Helps pinpoint performance problems coming from problems in code

• Tracing available in production minimizes need to reproduce problems in the lab

• Common view between developers and operations simplifies escalations

• Transparently instrument Spring applications at the code level

• Roll up data from multiple application nodes with filters and drill down

• Hyperic integration for unified operational view and robust alerting

Monitor

25

Application Visibility Answers Important Questions

How is my Hotel Booking app

performing?

Are the response times within expected SLAs?

Is there an issue with finding and displaying available hotel rooms?

Is the database a bottleneck?

Monitor

26

Platform Scale

Scale

27

Scaling Strategies

Horizontal

Vertical

Cloud

Scaling Strategies

There is no silver bullet:

Horizontal scaling requires module application

Vertical Scaling has it limits.

Cloud Scaling requires application portability.

Scale

28

Virtualizing Monolithic Applications – a good start

Avg CPU Utilization

Avg CPU Utilization

App A

Avg CPU Utilization

35%

35%

70%App BApp B

App C

App A

105%

Scale

29

Virtualizing Monolithic Applications – the goal

Avg CPU Utilization

Avg CPU Utilization

35%

35%

App B

App BApp BApp BApp B

App A

App AApp AApp AApp A

App A

App B

App B

App B

App A

Scale

30

Virtualizing Monolithic Applications – the goal

Avg CPU Utilization

Avg CPU Utilization

35%

35%

App B

App B

App B

App B

App B

App A

App A

App A

App A

App A

App B

App B

App A

Scale

31

Hybrid Cloud

Hybrid Cloud

Establish trusted partners

Ensure OPEN agreement both technical and legally.

Build application that are location transparent.

Scale

32

Cloud Bursting

App B

App B

App B

App B

App A

App A

App A

App A

App B

App B

App A

App A

App A

App B

App B

App A

App A

• Higher Hardware Utilization

Business Benefits

• Cloud ROI model• Flexibility• Response to Peak Demand

Scale

33

Avoiding Bottlenecks at the Data Layer

How to scale the data tier?

Scale

34

vFabric GemFire: Enabling Extreme Data Scalability

Application Data Lives Here

File Systems Databases Other Data Systems

Application Data Sleeps Here

Low-Latency, Linearly-Scalable, Memory-based Data Fabric

• Data distribution, replication, partitioning and colocation

• Pools memory and disk across many nodes

Data-aware Execution

• Move functionality to the data for peak performance

Active/Continuous Querying and Event Notification

• Changes are propagated to one or more "active" copies

Scale

35

Platform Integration

Integrate

36

Integrated Enterprise

Integrated Enterprise

Enterprise application are NOT silos but ARE integrated

Ensure your new cloud application can be integrated into your existing application .

Avoid the big bang approach

Integrate

37

Spring Integration

Problem: An enterprise service bus (ESB) is often overkill for most application integration scenarios.

Solution: Extend the Spring programming model to deliver EIP (Enterprise Integration Patterns)

Pattern Description

Splitter Split one message into multiple messages

Aggregator Combine multiple messages into a single message

Wire Tap Inspect point to point messages

CBR Route a message based on content

Transformer Transform message content into a different form

38

Trace, Monitor, Alert, Manage

Your [JavaSpring] App

Built withSpringSource Tool Suite

Hyperic &Spring Insight

RabbitMQMessage Brokers

AMQP, SMTP, XMPP, Stomp, …Point –to-point and pub-subVirtual hosts, dynamic config

Other clouds devices applications

Cloud scale message bus

Modern messaging for the cloud...Integrate

39

RabbitMQIntegrate

40

Summary

41

Enterprise PaaS – 7 Best Practices

1. Discover

2. Modernize

3. Define

4. Adopt

5. Monitor

6. Scale

7. Integrate

42

Goal of Platform as a Service (PaaS)

Friction-free deployment

No machines or middleware to manage

Latest high productivity frameworks

Choice of application services

Cloud portability

More responsive to developers

Elastic and dynamically scalable

Improved efficiency

Digest future cloud advances

Cloud portability

Application Developers

“Write code, not tickets”

IT Operations

“IT as a service provider”

Boost application

velocity

43

Next Steps?

www.cloudfoundry.com

www.vmware.com/go/vfabric www.vmware.com/services