essential requirements for a paas - · pdf filepaas criteria force azure cf vfabric cordys...

Essential Requirements for a PaaS

, © CSC 2012 - CSC Proprietary and Confidential

Renganathan Kasthurirengan

25-Mar-2012

Agenda

Cloud Models

Opportunities

Cloud – Emerging trends, Impacts and Drivers for Adoption

Requirements for PaaS

© CSC 2011 - CSC Proprietary and Confidential 2

Multi-tenancy

Comparison of Popular PaaS Offerings

Considerations in selecting PaaS

Moving existing applications to Cloud

CSC ACE Factory

The Cloud Opportunity: A Top-Down Approach

Business Process as a Service (BPaaS)

Goal: Achieve business agility and process innovation

Sponsor: Business Unit ExecsSoftware as a Service

(SaaS)

Goal: Improve functionality and ease of use

Sponsor: Business Unit and IT Platform as a Service

Increased Business Agility and


Sponsor: Business Unit and IT Execs

Platform as a Service (PaaS)

Goal: Develop and deploy applications faster

Sponsor: IT Development Management

Infrastructure as a Service (IaaS)

Goal: Handle peak loads cost effectively

Sponsor: IT Infrastructure Management

Agility and Cost Savings as Companies Move Up the Stack

Opportunitiesfor Enterprise Savings and Capabilities

60%

70%

80%

90%

100% Optimized infrastructure

Optimized business process operations, capacity, and standards

Increased multi-tenancy

Dynamic brokerage of commodity capacity

Increased enterprise business process

Expand/contract elasticity

Multi-provider integration

Target platform for rationalization/standardization

Traditional ITO

On-premise virtualization

Consulting-heavy Custom & ERP

Offshore

30%30%

20%20%

80%80%

30%

20%

80%

Savings

40%40%

60%60%

40%

60%

Savings

SavingsBusiness Process OpsBusiness ApplicationsERPSourced InfrastructureInternal Infrastructure

Agility

50%50%SavingsSavings

50%50%

50%Savings

50%20%20%

30%30%

20%

30%


0%

10%

20%

30%

40%

50%

Today Wave 1 Wave 2 Wave 3

process integration

Enhanced operational resilience

Accelerated time to market

Reduced capital expenditure

Reduced facility footprint

Offshore apps support

Considerable heterogeneity

10%10%

10%10%

10%10%

20%20%

10%

10%

10%

20%

10%10%

10%10%

5%5%

10%10%

25%25%

10%

10%

5%

10%

25%

Wave 2SaaS – Enterprise + Business Apps

Cloud Broker

Wave 1IaaS + PaaS

Wave 3BPaaS

Today

10%10%

5%5%

10%10%

20%20%

50%50%

5%5%10%

5%

10%

20%

50%

5%20%20%

20%20%

10%10%

20%20%20%

20%

10%

20%

Emerging trends – Cloud Impact in the new Enterprise

Cloud enables mobilityCloud enables mobility

• Mobility now mainstream (HTML5 for best end user experience)

• Mobile phones and PDAs will continue to attract people to cloud-based services

Cloud will be the fabric of integration and delivery. Cloud will be the fabric of integration and delivery.

• Rise of third-party integrated services for leveraged business models

New ways of developing applications New ways of developing applications

• Pay-as-you-go infrastructure is just table stakes!PaaS is the way forward, with up to 40% cost reduction in application run and maintain.


• Future cloud application: agile, unique, easy to use, and affordable

• Content volume will increase five-fold from today; data and storage virtualization will be the norm

• Social media is the “glue” for efficiency

• Analytics equals knowledge

• People will not be able to distinguish between working on their local devices and working in the cloud

• Hybrid clouds are the most common and secure delivery vector

Some Security/Privacy concernsSome Security/Privacy concerns

• Privacy and IP protection would be the main concern and potential barrier. Edge access from mobile to cloud is being simplified by development of trust protocols and IAM as services

Top Drivers for Adoption of Cloud Computing

• Based on a recent global survey funded by CSC …

• 3645 IT decision makers surveyed

• Top Drivers

• 33% - Mobility


• 33% - Mobility

• 21% - Speed of Business

• 17% - Cost

• 93% saw improvement in IT performance after cloud adoption

• Most Small organizations cited Mobility as the driver and large organizations sited cost savings

Cloud Workloads – Key Questions and Concerns (1)

Stakeholder Impact

• Will my customers be impacted – downtime, app response, usability, etc.?

• Which business processes are right for Cloud? What is the impact?

• Which providers offer the right level of SLAs, security and governance for my business? What about app security and data confidentiality?

• Does this impact my current support workforce?

• Can I shift to a different Cloud provider if the need arises?

• What’s the impact on procurement and what should I consider before signing up?

• How do I orient my internal users to adapt to Cloud based services?

• What are some of the organizational lessons learnt from Cloud adoption initiatives


• What are some of the organizational lessons learnt from Cloud adoption initiatives at other companies?

Cost Analysis

• What are the cost savings of moving the app to Cloud as compared to current spend?

• How do I monitor on-going fees and how much would it cost at peak business periods?

• Will I save on software licensing costs?

• What are long-term costs associated with the Cloud?

• How much should I budget for end-user orientation and additional training for support staff?

Cloud Workloads – Key Questions and Concerns (2)

Technical Suitability

• What changes are needed to move the app to Cloud?

• What is the complexity of the change and risk associated?

• How will the Cloud app integrate with my on-premise resources?

• What about app performance? How do we handle latency issues?

• How do I setup single-sign-on user authentication for the app on the Cloud?

• How do I upload large data sets to a Cloud environment?

• What about my legacy Mainframe applications? Can they be Cloud-enabled?

• I have a lot of batch programs. Can they be processed on a Cloud environment?


• I am building a mobile app strategy. Can Cloud services be leveraged?

Operational Readiness

• How do I prioritize and build a plan to leverage Cloud for my apps?

• How can I provision and control resources for apps? How do I manage them?

• Is there a different licensing model for software on the Cloud?

• How can I setup multi-level user security for access and control?

• How do I keep a tab on Cloud resource usage? How will it be metered and billed?

• How do I orchestrate between multiple Cloud providers, if I choose to use more than one?

• Who is responsible for supporting the app on the Cloud – the Cloud provider or my staff?

• What new skills would I need to support the Cloud model?

Requirements for PaaS

Multi-tenancy – all layers, seamless multi-tenant programming

Multi-tenant automatic and Elastic resource allocation

• Computing resources allocated and de-allocated to applications on-demand.

• On demand –automatic multi-tenant provisioning – based on SLAs,

• Auto-scale – span across more machines, down-scale when needed, Auto-rebalancing

Self Service, tenant aware configuration, customization, versioning

Fine Grained control of computing resources, usage tracking, monitoring and billing


Fine Grained control of computing resources, usage tracking, monitoring and billing

• Monitoring application behavior, event handling, trouble shooting,/error recovery,

• Protection of Tenant SLAs,

Extreme transaction processing (XTP)-grade performance characteristics, Global-class interoperability and access models

Tenant-aware protections of security, privacy, integrity

Portability

• Avoid Vendor lockin, Portability between Public and Private Clouds, choice of cloud provider, programming languages, databases, standards based APIs

• (Adopted From Gartner Research : Key Issues for Cloud-Enabled Application Infrastructure)


PaaS Criteria Force Azure CF vFabric Cordys JBoss

Public/Private Public Public Public BetaPrivate,

Private Public/ Private

Public (openShift), / Private

OS Windows

Linux

Windows Azure Ubuntu,

Windows (Uhuru)

Windows, Linux

Windows, Linux

RH Linux, Windows

Languages Apex

Visual Force,SOQL

C#,VB.Net Java, Ruby, Groovy, PHP, Python

Java, Ruby, Java, PHP, Python (Express)

Frameworks/Standards

WebServices, SAML, REST

.Net 3.5, 4, SAML, WS, REST, sHTML

Spring,Grails, , Rails, Node.js,JEE5,REST,HT

ML5

Spring, Node.Js,JEE5, REST,

HTML5

WS, SAML Spring, Seam, JEE6,REST,

HTML5


ML5 HTML5 HTML5

Databases Force.com DB, external DB

SQLAzure, Azure Data Services

MySQL, PostgreSQL,MongoDB,Redis

Gemfire, SQLFire

Oracle, SQL Server, MySQL

MySQLMongoDB

BPM, Messaging, Integration

WebservicesAPI, mashups, outbound messaging,

WFFoundation, Service Bus, Azure Queues

RabbitMQSpring Integration

Spring Integration, RabbitMQ

BPM , ESB, Mashups, MDM

JBPM, JBoss MQ

RAD, Web 2.0, Social Media

Force.com Builder, VisualForce,SiteForce, Flex

Light Switch Wavemaker, Roo, Spring Social Media

Wavemaker, Roo, Spring Social Media

Composite Application Framework,XForms

Other developer tools

Force.com IDE,

Force.com

Sandbox,

codeshare

Visual Studio,

TFS

Eclipse, STS,

Code2Cloud,

MicroCloud

Eclipse,

STS,

Code2Cloud,

Eclipse, GIT


PaaS Criteria Force Azure CF vFabric Cordys JBoss

Auto provisioning,

scaling

Available Scripting and confiugration

Hyperic , Health

Manager, Scripting using VMC

Hyperic and scripting using VMC

SOA grid architecture built in provisioning,

scaling

Limited

Multi-tenancy Multi-tenant meta-data driven DB

Shared hardware

Shared Hardware

Shared Hardware

CCP –Sharedeverything to Shared nothing

Not Available


Monitoring,

Tracking, Billing

System Center, No billing

Hyperic, Health Manager. No billing

Hyperic. No billing

Cordys BAMProcess Monitor

Flex consoleBilling not available

Tenant aware

security, privacy

Not available

Not available Not available Available Not available

XTP, Global Class

interoperability

Not available Azure Cache

Not available Gemfire Not available JBoss Cache, MemCache

Portability No No Yes Yes Yes Yes

Seamless

Production

Deployment

Yes Yes Yes Yes Yes Express has the capability

Other PaaS Platforms

• Google

– Java (a restricted environment), Python and Go (Beta)

– Cloud SQL (MySQL)

– BigTable (No SQL)

• Oracle

– Public cloud as Beta


– Public cloud as Beta

– Entire Oracle enterprise platform made available on cloud

• Amazon Elastic Beanstalk

– Tomcat Server on EC2

– Elasticache

– RDS (Relational Database Service) supports multiple RDBMS

– Simple DB(No SQL)Bring your own DB (IaaS deployment)

Who needs PaaS

Enterprises

• To run their business critical workloads and workloads that need cloud scalability

• Workloads that need Enterprise grade security

• Speed to market and agility to bring out new products, regulatory compliance needs

• Support multiple form factors

• Understand change in customer preferences/behavior and adapt faster,


• Understand change in customer preferences/behavior and adapt faster, respond faster to risks, crisis and opportunities

• Move legacy applications to a secure and scalable platform

ISVs

• To SaaS enable their applications, providing a secure multi-tenant environment

• A cost effective, single instance globalized application

• Scalability and performance

• Always on infrastructure

• Mutiple form factors

Considerations in Selecting PaaS

• Enterprise Architecture

– Business Process requirements

– Data Architecture (Transaction processing, BI, Analytics)

– Integration Needs

– Security, Privacy Needs

– Open Source Policies

– Globalization, Distributed Processing

– Collaboration, Mobility needs

– Multi-tenancy, Metering, Billing Needs


– Multi-tenancy, Metering, Billing Needs

• Enterprise Application Portfolio

– Need for moving existing applications to cloud

– Life and technology landscape

– How aligned they are to business

• Available Skills

• Total Life cycle Costs

– Includes hardware, license, support, Development and Maintenance costs, Migration costs, obsolescence costs, opportunity costs associated with Time to Market

Implementing Multi-tenancy – A Typical Approach

Shared Auth Schema

SchemaTenant A Schema

Tenant B Schema

VMware tcServer

Application

Tenant A

1

2

1 & 23

3

4 4

Oracle 11g instance in VM


1. User belonging to Tenant A sign in to the application using user id, tenant id and

password and server authenticates against Shared Auth Schema and sends

Tenant A App schema details

2. User belonging to tenant B B sign in to the application user id, tenant id and

password and Server authenticates against Shared Auth Schema and sends

tenant B App Schema details

3. Tenant A user perform application business operation, data gets stored in

Tenant A App Schema

4. Tenant B user perform application business operation, data gets stored in

tenant B App Schema

SchemaTenant B

CSC Positioned in Leaders Quadrant for Public Cloud Infrastructure as a Service Magic Quadrant Report

CSC Infrastructure as a Service — CloudCompute


Source: Gartner (December 2011)

What is ACE?

• ACE (Application Cloud Enablement) is CSC’s blueprint for accelerating the migration of legacy applications to the cloud and developing new applications on the cloud

• Composed of a suite of CSC services that span the shape-transform-manage lifecycle, ACE enables clients to quickly and economically benefit from the scale and elasticity of cloud computing.

ShapeShape TransformTransform ManageManage


Identifies which applications and business processes would benefit

from running in the cloud.

Determines the appropriate transformation treatment for each

application.

Creates the detailed application and data transformation plan.

Identifies which applications and business processes would benefit

from running in the cloud.

Determines the appropriate transformation treatment for each

application.

Creates the detailed application and data transformation plan.

Applies the appropriate treatments to transform and modernize the client’s

applications.

Utilizes CSC’s unique automation and IP for greater speed, reduced cost,

and higher quality of transformation.

Applies the appropriate treatments to transform and modernize the client’s

applications.

Utilizes CSC’s unique automation and IP for greater speed, reduced cost,

and higher quality of transformation.

Provides the scalable IaaS or PaaS environment for the transformed

application.

Delivers application maintenance, support, and

enhancements for the applications running in the cloud.

Provides the scalable IaaS or PaaS environment for the transformed

application.

Delivers application maintenance, support, and

enhancements for the applications running in the cloud.

Application Cloud Enablement Treatments

REFACTOR Alter the application’s design while retaining functional equivalency

CONVERTAlter the application’s technology while retaining functional equivalency (e.g., change language, operating system, data storage technology)

REBUILDRediscover the application’s business requirements and redevelop the application from the ground up

REHOSTMove the application from one technical environment to another with no or very little change to code (“lift and shift”)

TransformTransformShapeShape ManageManage


little change to code (“lift and shift”)

REVISE Refactor the application while also developing new business capabilities

REPLACEIdentify a COTS product or SaaS alternative to replace the application’s business capabilities and migrate data to the new systems

CSC’s Industrialized Treatment Capability

ACE Factory

Assembly Line Capability

Refactor

TransformTransformShapeShape ManageManage

ACE Factory is an industrialized, automated, managed service that quickly analyzes, transforms and tests an organization’s legacy custom and mainframe business applications for cloud deployment.


Treatment Workflow

Treat

ITIL Service Model/Common Transformation ModelITIL Service Model/Common Transformation Model

Ready Now

Source Source

PlanPlan PreparePrepare

TestTest

Ready Now Validation

Ready Now Validation

ReleaseReleaseTransformTransform

SHAPESHAPE MANAGEMANAGE

Analyze&

Price

Analyze&

Price

Target Target

Refactor

Rebuild

To Factory

ACE Factory – Source – Target Pairs

Source Applications

Target Platform Transformation Approach

Roadmap Plan

Mainframe , AS/400

COBOL applications

•VFabric, Cloud Foundry

•Micro Focus server

•JBoss Open Shift

•Force.com

•MS Azure

•Transformation to Java or

.Net

•Tool based transformation

•Rebuild after extracting

Business Rules

•QTE enhancements

•Re-factor to improve code

quality

•Identify other tools –

Alchemy

Legacy Client Server

Applications

(PowerBuilder, Oracle

Forms, Delphi, VB)


•JBoss

•Force.com

•MS Azure

•Transformation to Java

•Tool based transformation

•Rebuild after extracting

Business Rules

Identifying new tools such

as Make solutions,

Nexaweb etc


Legacy Java

applications


•JBoss, Force.com

•Cordys

•QTE tool Enhancement

•Oracle to be brought in

Legacy .Net

Applications

•MS Azure •Transformation to Azure

using MS specific tools

Cloud Application

Development


•Force.com, Cordys, Azure

•Development using RAD

tools as provided by PaaS

Use of Rapid development

tools to enhance

productivity

Process

Enhancements

•All •All •Performance, Security

Testing

•ALM Automation

•Agile Approach

ACE Factory Transformation Using Q-TE

Audit & Consistency

Report

Business Model

ReviewStandards Interfaces

Screen Amalgam.

SpecificationDeployment

Metadata Client Interaction


SOURCE TARGET

RepositoryIteration Loop

Transform DeployParse

ACE Factory Animation


essential requirements for a paas - · pdf filepaas criteria force azure cf vfabric cordys...

Documents