scale cloud across enterprise

Scale Cloud Across the Enterprise

Chris Haddad

Vice President, Technology Evangelism

Follow me on Twitter @cobiacomm

Read architecture guidance at http://blog.cobia.net/cobiacomm

Skate towards the puck

Business Value

Best Practice Adoption

Process Repeatability

Fast time to value

3

Cloud Business Value For Development Teams

• Lower development barriers

• Lower adoption barriers

Best Practice Adoption and Process Repeatability

• Cost-effective, development, collaboration, and

deployment infrastructure enabling a long tail of

application development

• A shared environment for cross-organization

application development and delivery

• Infrastructure enabling user experience composition

across multiple disparate application providers

Fast Time to Value – Increase Agility

• Rapidly adapt and fulfill new market demand

• Reduce time to introduce new services,

applications, and products into long tail market(s)

04/11/2023 6

Enterprise Architecture Business Model Challenges

• Unable to cost-effectively support long tail of

application delivery

• Lack of metrics and baseline measurements

• Limited ability to influence adoption

• High friction and interaction cost when building

cross-team business processes

• Inability to capitalize on business opportunities

due to long IT solution lead times

Cloud Business Value Blockers

• Silo owners

• Adoption curve

• Trust barrier

• Unknown baseline

• Funding model

Source: http://blog.industryweapon.com/2010/01/beware-of-the-business-blocker/

8

To succeed and scale Cloud – Build a Digital Ecosystem Platform

Digital Ecosystem

Your Core Business Capability

3rd Party Partners

DevOps Forge and

Governance

Cloud Deployment App Store

Personalized SaaS Solution

Your Digital Business

Ecosystem

04/11/2023 9

New Enterprise Architecture Approach

• Self-organization

• Crowdsourcing – source apps and capabilities from crowd

• Dynamic distribution channels and fluid connections

• Adaptation and evolution

• Local autonomy leading to unforeseen ecosystem partner extensions

• Spontaneous selection and aggregation across services and solutions

• Low interaction cost

• Frictionless information flow

• Enables cost effectively serving a smaller, niche audience

Recommendations from the Coach

Business Value

Best Practice Adoption

Process Repeatability

Fast time to value

11

Cloud Business Value For Development Teams• Lower development barriers

• Provide on-demand Application Development project infrastructure and run-time environments

• Catalogue of re-usable open APIs, cloud services, and domain frameworks

• Lower adoption barriers • On-demand web application and Cloud API subscriptions

via a self-service provisioning portal• Establish searchable registry of app, service, api, and

data descriptors• Reliable, available, and scalable solutions

Best Practice Adoption and Process Repeatability

• Cost-effective, development, collaboration, and deployment infrastructure enabling a long tail of application development• Architecture templates and application platform services

• A shared environment for cross-organization application development and delivery• Governed, iterative lifecycle management across hybrid

clouds and composite applications

• IT Business performance metrics and analytics

• Infrastructure enabling user experience composition across multiple disparate application providers

Fast Time to Value with On-demand Contextual Personalization

• Increase agility

• Rapidly adapt and fulfill new market demand

• Reduce time to introduce new services, applications, and products into long tail market(s)

• On-demand Contextual Personalization

• Information access and social network access privileges• Information aggregation and composition• Business processes and rules• Service levels, Quality of Service, and monetization rates• Security policies

Fast path to goals!

Cloud DevOps Factory

Platform as a Service

API Management

Business Activity Dashboards

Embrace DevOps Processes

• Self-service configuration

• Automated provisioning

• Continuous build

• Continuous integration

• Continuous delivery

• Automated release management

• Incremental testing

04/11/2023 16

Command Line Compilers and Linkers

Integrated Development Environments (IDE)

Application Lifecycle Management (ALM)

Development Forges

Cloud

Factories

Time

Scale best practices with Cloud Factories

2012+

What is a Cloud Factory?

A Cloud-based, automated, DevOps approach to agile application design, development, delivery, and visibility

• Simplifies the developer experience

• On-demand self service and Cloud provisioning

• Continuous build, continuous integration, continuous test, and

continuous delivery

• Governed, iterative lifecycle management across hybrid

clouds and composite applications

• Architecture templates and application platform services

• IT Business performance metrics and analytics

• Builds a Digital Business Ecosystem

• Enable a long tail of application development

• Fosters cross-organization development collaboration

04/11/2023 18

Open Source DevOps, Agile, and Cloud Tooling

Project and Team

Management Software development

workflow

Governance and

Compliance

Development Dashboards

Develop Code

Issue Tracking

Source Control

Continuous Build

Continuous Integration

Test Automation

Continuous Deployment

• Resource monitoring• Resource management

• Performance management

• Traffic orchestration

• Metering• Reporting• Billing

• Service catalogue• Service tiers

• Demand and capacity management

• Lifecycle management• Infrastructure Authority

integration

• Self service configuration

• Automated provisioning• Policy configuration• Process automation

Dev Ops Tooling

Automated Governanc

e

Service Level Management

Consumption based Funding

Platform as a Service Capabilities

Cloud-aware Reference Architecture

Cloud Platform

Cloud Management

PaaS Manager

Cloud Governance

Identity Management

Asset Repositories and Registries(tenant code,

service endpoints, meta-data, configuration, policies)

Infrastructure as a Service (AWS, Eucalyptus,

OpenStack, CloudStack)

Platform as a Service Run-time Framework (i.e. WSO2 Stratos, Cloud Foundry, RedHat OpenShift)

Service-aware, tenant-aware

Elastic Load Balancer

Stratos Controller

Asset/Code Deployer

Asset/Code Synchronizer

Metering and Billing

Cloud Native Container(s)

Application Platform Services (web server,

database, ESB)

Tenant 1

Tenant (n)

Platform as a Service Reference Architecture

Carbon ESB

Cartridge

Carbon App ServerCartridge

Stratos Controller

MessageService

LoggingService

SecurityService

RegistryService

RelationalData

Service

Elastic Load

Balancer

Cloud Controller/Autoscaler

Artefact DistributionController

DeploymentSynchroniser

ManagementConsole

ColumnStorageService

FileStorageService

Task Mgmt

Service

BillingService

Other Carbon

Cartridges

PHPCartridge

Any PluggableCartridge

Infrastructure Cloud (EC2, vmWare, Rackspace, OpenStack, Eucalyptus, etc)

Load Monitor

IaaS

PaaS

Fou

nd

ati

on

aPa

aS

iPaaS

Cloud API promotion, exploration, subscription, and collaboration

On-demand self-service access to approved Cloud Services and APIs

Explore Cloud Services and APIs

Business Activity Dashboards

TODO

Business Activity Monitoring

Cloud Strategy Goals

1. Decrease solution provisioning time

2. Right-size infrastructure, improve resiliency, and enhance Quality of Service (QoS)

3. Accelerate software development iterations

4. Share across multiple users and groups

5. Integrate and bridge heterogeneous Cloud environments

6. Optimize Cloud footprint and lower application cost

Cloud Characteristic Roadmap

Cloud

On-demand

Self-service

Multi-tenancy

Service Catalogue

Elastic Scalability

Provisioning

Activity Monitoring

Resource Pooling

Usage Policies

Federation

Consumption based Funding

Portfolio Models

Metering and Billing

29

7 +/- 2 Objectives

1. Engage stakeholders in a collaborative development workspace

2. Promote best practice workflow, architecture, and governance practices

3. Deploy applications into a Cloud run-time environment

4. On-demand application subscriptions via a self-service provisioning portal

5. Share applications across multiple tenants (e.g. departments, workgroups, employees, partners)

6. Scale run-time to meet usage

7. Deploy Open APIs

8. Encourage API adoption via API Store

9. Track business activity and analyze Cloud service usage, performance, and cost

ResourceTier

Sharing Business Capabilities at Scale

Functional Role

Client Tier

Integration Services

Integration ServicesResourceServices

Functional Role

Presentation and Mashups

Functional RoleFunctional

code

Presentation RolePresentation

and MashupsPresentation and Mashups

ResourceServices

Private Applications

Public Cloud Services

Business ProcesBusiness

ProcessBusiness ProcessBusiness Process and

Business Rules

Scaling through API composition

Mobile Application

Application Portfolio

Hybrid Platform Services

Presentation Services

Resources Services

Functional Services

Business Process and

Rules Services


Composite Application

Business Service Portfolio


Cloud API Endpoint

Infrastructure as a Service (IaaS)

SaaS Application

Web applicationEndpoint

Scaling across Regions and ZonesMultiple IaaS (hybrid) Deployment

Availability

Cost

LOWEST

HIGHEST

32

Private cloud (data center)

Zone 1

Zone 2

Amazon EC2

Zone 1

Zone 2

Rackspace Cloud

Zone 1

Zone 2

33

Cloud Scale = High Availabilityat a cost

Sin

gle

No

de

Pri

ma

ry-S

eco

nd

ary,

sin

gle

LB

Mu

lti-n

ode

act

ive

cl

ust

er

- S

ing

le z

on

e Mul

ti-re

gion

Pri

ma

ry-S

eco

nd

ary,

with

mu

ltip

le L

Bs

Mu

lti-z

one

Mu

lti-I

aaS

Scaling Best Practices

New-Normal Cloud architecture practices

• Distributed and federated interactions

• Event based, heterogeneous systems, network latency

• Configurable containers and engines

• Declarative data, rules, and process definitions

• De-normalized and simplified data models

• Hadoop/BigTable, Hypertext media, simple NoSQL entities

• Expect failure

• Systems span transactional control

• Applications decomposed into distinct services

• Federated environment drives autonomy, statelessness, and composition

Mission-critical Cloud requires new architecture components

Availability Scalability Management

State replication Tenant partitioningPrivate jet mode

Management nodes

Session replication Ghost deployment Logging infrastructure

Multiple load balancers withkeepalived or DNS RR

BAM 2.0 architecture Deployment synchronization

Auto-scaling

Elastic Load Balancer

Tenant-awareness impacts Cloud Scaling

Tenant Scaling Method Impacts Value Proposition

Single Application Tenant per

Dedicated Application Server Container

Container 1

Tenant 1

Container 2

Tenant 2

Container 3

Tenant 3

Container 4

Tenant 4

Multiple Application Tenants per Shared Application Platform

Service Container

Container 1

Tenant 1

Tenant 2

Tenant 3

Tenant 4

Container 2

Tenant 5

Tenant 6

Tenant 7

Tenant 8

Container 3

Tenant 9

Tenant 10

Tenant 11

Tenant 12

Container 4

Tenant 13

Tenant 14

Tenant 15

Tenant 16

Cloud Topology and Value

Tenant Context

Container

Tenant Partition

Application Solution Tenant Traffic

Tenant-1

AS-1

Tenant-1

ESB-1

Tenant-1

Tenant-2

AS-2

Tenant-2

ESB-2

Tenant-2

Tenant-3

ESB-3

Tenant-3

Five (5) Container Instances, Three Tenants

Cloud Topology and Value

Tenant Context

Container

Service Partition

Application Solution Tenant Traffic

ESB

ESB-1

Tenant-1 Tenant-3

ESB-2

Tenant-2

Web Application

AS-1

Tenant-1 Tenant-2

Three (3) Container Instances, Three Tenants

Scaling a Cloud Business

Measuring Revenue versus Cost

Source: http://giffconstable.com/2009/11/freemium-business-model-template/

Scale Strategy and Tactics

• Gain Credibility

• Demonstrate improved resiliency and QoS

• Converge teams

• Offer standard shared application platform services

• Establish and promote the service catalogue

• Be inclusive

• Support multiple development languages, environments, and use cases

• Lower barriers to entry (e.g. financial, tooling, skills)

42

7 +/- 2 Objectives

1. Engage stakeholders in a collaborative development workspace

2. Promote best practice workflow, architecture, and governance practices

3. Deploy applications into a Cloud run-time environment

4. On-demand application subscriptions via a self-service provisioning portal

5. Share applications across multiple tenants (e.g. departments, workgroups, employees, partners)

6. Scale run-time to meet usage

7. Deploy Open APIs

8. Encourage API adoption via API Store

9. Track business activity and analyze Cloud service usage, performance, and cost

Questions?

43

http://www.flickr.com/photos/oberazzi/

Measuring Value

• Time

• Cost

• Resources

Key Metrics

FoundationTime to create new application environment

Time to redeploy application

• OptimizeMinimum and maximum scale

Scale frequency (i.e. time to scale up/down)

• TransformationTime and effort required integrating business process, event

processor – creating a complex app.

Time and effort required to apply policy across tenant(s)

Cost to operate application per user or transaction

What is your value baseline?

Quick Start Use Cases

1. DevOps Tooling and On-demand self-service

2. Automated Governance

3. Service level management and elastic scale

4. Consumption based pricing and billing


DevOps Tooling and On-demand self-service

• Use Cases

• Rapidly provision application environment

• Rapidly provision application tenant

• Allocate, provision, monitor, manage, and administer resources across multiple tenants, nodes, and locations

• Develop complex, composite integrated applications

• Key metrics

• Time to create new application environment

• Time to redeploy application


Automated Governance

• Use Cases

• Create users and configure rights

• Deploy on preferred topology that meets deterministic performance requirements (e.g., replication, utilization, latency, bandwidth, and coherency)

• Create service throttling and security governance (XACML) policies

• Key Metrics

• Time and effort required integrating business process, event processor – creating a complex app.

• Time and effort required to apply policy across tenant(s)


Service level management and elastic scale

• Use cases

• Ensure application satisfies consumer demand while maximizing resource utilization• Scale workload processing and increase performance while

minimizing infrastructure spend

• Load test application service

• Demonstrate multi-tenant web application

• Key Metrics

• Minimum and maximum scale

• Scale frequency (i.e. time to scale up/down)


Consumption based pricing and billing

• Use cases

• View service logs

• View bill by business value

• Key Metric

• Cost to operate application per user or transaction