Creating an Ecosystem Platform with Vertical PaaS

Chris Haddad Vice President Technology Evangelism

Follow me @cobiacomm Read more about PaaS at http://blog.cobia.net/cobiacomm

Try StratosLive https://stratoslive.wso2.com/

Creating an Ecosystem Platform with Vertical PaaS

• What is Platform as a Service?

• Why create an ecosystem platform?

• The need for API Management, API Store, and API governance

• What is Vertical Platform as a Service?

• Getting Started and Measuring Success

What is Platform as a Service?

Cloud Characteristics and Architecture

Resource pooling

• Multi-tenancy

• Resource utilization

• Shared, virtual infrastructure

• Interoperability

On-demand

self-service

• Flexible workload assignment

• Standard service offerings

• Quick startup and automation

Rapid Elasticity

• Stateless services

• Rapid provisioning

• Flexible topology

• High Quality of Service

Measured service or pay per use

• Fine-grained metering

• Billing • Reporting

• 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 Governance

Service Level Management

Consumption based Funding

Platform as a Service Capabilities

Shared Middleware Services

Business APIs

“APIs creates a way to make resources available for internal and external partners to access information and services.”

Web Ecosystem Platforms and APIs instead of Web Sites

• Dynamic experience instead of static views

– Facebook instead of mySpace

• Commerce storefronts instead of affiliates

– Amazon instead of Barnes&Noble

– eBay instead of WalMart

• Business capabilities (exposed as APIs) are

– Easy to subscribe, provision, personalize, consume, and monetize

Don’t ignore API Proliferation

Source: http://blog.programmableweb.com/2011/10/03/4000-web-apis-whats-hot-and-whats-next/

The New Web

Source: http://blog.programmableweb.com/2011/01/03/api-growth-doubles-in-2010-social-and-mobile-are-trends/

Create an Architecture of Participation across multiple brand name properties

Vertical PaaS: “Your Business as a Service”

• Based on real projects that WSO2 is running • Beyond APIs – because it creates a shared

governance model and runtime • An opportunity to add significant value to

partners: • A complete environment that they can customize • Not just the look and feel but also the behaviour • An ideal platform for shared revenue

• A shift in business models enabled by cloud technology

New Requirements

API Store

API Store

API Store Front

API Store Dashboards

API Store Back Office

Common Environment Services

Identity Server and Key

Management

API Governance

API Registry Repositories

• API discovery and recommendation

• Requirements matching

• Review ratings and comments

• Funding gate

• Approval gate

Design

• Developer on-boarding

• API integration

Build and Test • Upgrade notification

• API monetization

• On-board new consumers

Deploy

• Developer credential provisioning • API access provisioning • API meta-data storage • Asset promotion and demotion

API Management Solution

Enterprise Application Development Environment

Enterprise Application

Development

Environment

API Developer

API Store

API Development

• Governance

• Description

• Collaboration Tools

API Versioning

API Management

Credential Management Vertical PaaS

• API

• Domain Capabilities

• Tenant Configuration

Portfolio Management

Dashboards

• Operations

• Development

• Monetization

DevOps Tooling

SVN / Git Eclipse

API Provisioning

and configuration

Vertical Ecosystems

Vertical PaaS

Vertical Application 3 M

an

ag

ed

by P

aa

S

Tenant

Pers

onaliz

atio

n

OS/Hypervisor

Containers

Hardware

Programming Languages

Frameworks

App Source Code

App Data

Ve

rtica

l

AP

I

Domain API

Domain Artifacts

App

Configuration

Domain API

Domain Artifacts

App Source Code

App Data

App

Configuration

App Source Code

App Data

App

Configuration

Vertical Application 1 Vertical Application 2

Tenant / Consumer Personalization Dimensions

• Information access privileges

• Information aggregation and composition

• Social network access privileges

• Business processes and rules

• Service levels and Quality of Service

• Security policies

• Monetization rates

Vertical PaaS Business Perspective

• Customer has a set of APIs

• Due to industry regulations, the APIs are read-only

• Difficult to get real value

• A Vertical “Business” PaaS creates an ecosystem where:

• Partners can create/customize betting applications

• Shared governance and regulatory environment

• Shared revenue

Vertical PaaS: Technical Details

• A deployment of:

• Stratos

• Enterprise Application Development Cloud

• Three Stratos runtime containers:

• Dev, Staging, Production

• Each an Elastically Scaled, Metered, Multi-tenant Cluster

• A single Stratos Controller (Identity, Registry and Load Balancer)

• Carbon components managing the Enterprise Application Development Cloud:

• Registry, ESB and BPS

• Together with Eclipse (IDE), Redmine (Project Management), JIRA (Task Tracking), SVN (code repository), Maven (Build)

• Each “customer project” is a “Stratos Tenant”

Sample governance process

• Projects are initiated via Redmine (Project Management)

• Actions in Redmine initiate Processes running in WSO2 Business Process Server • via Adapters in WSO2 ESB (also to JIRA, SVN, and Stratos)

• Includes user provisioning, governance processes, build and deploy

• User can deploy code into the Dev Environment directly from Eclipse

• When the user “deploys” code from Eclipse it initiates a 4-step approval process:

• Code review, Security, Compliance, System Test

Business Drivers for Vertical PaaS

• Pre-build Vertical APIs and Vertical PaaS components decrease time to market

• Vertical PaaS enables business domain experts to create and extend APIs

• PaaS frees developers from infrastructure decisions

Like an App Store based around your competencies – Increased opportunity for ecosystems to emerge

– Increased opportunity for shared revenue

– Partners will leverage your core competencies in new ways that you haven’t even thought of

22

Beyond APIs: “Your Business As A Service”

PaaS / Stratos

Existing business systems as APIs

Tenant

Apps

Tenant

Apps

Tenant

Apps

Tenant

Apps

Eco

syst

em O

wn

er

Part

ne

rs

Use

rs

API Management / API Store

Getting Started

• Identify core business API

• Build extensible, configurable API

• Publish API in API Store

• Foster business partnerships with API management on-demand self-service

• Host API on a multi-tenant platform

• Facilitate per-tenant configuration with API provisioning and API configuration

Measuring Success: Without an Ecosystem Platform

Teams re-build rather than re-use • APIs proliferate (100s of APIs)

– and are minimally re-used

• Minimal communication and coordination • Who is consuming API? • Who is writing re-usable APIs?

• Prevalent SOA Anti-patterns – Not Invented Here (NIH) – Tight Coupling – Build again

• Shared API invisibility – Teams do not know about API – Non-functional and functional requirements are not well

documented – Teams can not easily map APIto business capabilities

“Your Business”-as-a-Service summary

• Inherent deep multi-tenancy enables ecosystem plays • Not just shallow per-tenant customization

• E.g. eBay Stores, Amazon Sellers

• But significant per-tenant customization

• Client success stories demonstrates key aspects: • Ecosystem creation

• Shared governance and revenue model

• Significant benefit beyond APIs

• Cloud Development

• Automated Governance

Resources • Try Stratos right now:

– https://stratoslive.wso2.com/

• Read about Stratos: – http://wso2.com/cloud/stratos/ – Source Download available

• White Paper – Selecting Platform as a Service

• Blog Articles – What is Platform as a Service? – PaaS Evaluation Framework for CIOs and Architects – How to simplify Platform as a Service Complexity – Searching for Cloud Reference Architecture

• Contact us: – bizdev@wso2.com

One Enterprise Platform wherever you need it:

WSO2 Carbon On Premise: • In Production at Fortune

1000 companies • Handling 1bn

transactions/day • The only modular open

source middleware stack • Everything you need to

build Enterprise Applications

• From Core Logic to Mobile Apps

WSO2 Stratos In Private Cloud: • A single managed platform • Elastic, Self-Service, Multi-

tenant • Accelerates your private

cloud beyond virtual machines to provide real Enterprise Cloud Services

• Use only what you need

WSO2 StratosLive As a Service in the Public Cloud: • We manage, run and

maintain your application platform

• Complete Pay as you Use • ESB-as-a-Service • Governance-as-a-Service • Identity-as-a-Service • With appropriate SLAs and

simple monthly billing

• A single code continuum • Completely modular based on OSGi • Complete Enterprise SOA Architecture:

• AppServer, ESB, Governance, Portal, BPMS, BAM, Identity and more • Supported 24x7 with phone, web and full SLAs