1. 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/

2. 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

3. What is Platform as a Service?

4. Cloud Characteristics and Architecture
• Stateless services
Measured service
• Rapid provisioning
or pay per use • Flexible topology
Rapid • High Quality of Service
Elasticity
• Fine-grained
metering
• Billing
On-
• Reporting demand
self-service
• Flexible workload assignment
Resource pooling
• Standard service offerings
• Quick startup and automation • Multi-tenancy
• Resource utilization
• Shared, virtual infrastructure
• Interoperability

5. Platform as a Service Capabilities
• Self service configuration • Service catalogue
• Automated provisioning • Service tiers
• Policy configuration • Demand and capacity
• Process automation management
• Lifecycle management
• Infrastructure Authority
Dev Ops Automated integration
Tooling Governance
Consumption Service Level
based Funding Management
• Metering • Resource monitoring
• Reporting • Resource management
• Billing • Performance management
• Traffic orchestration

6. Shared Middleware Services

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

8. 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

9. Don’t ignore API Proliferation
Source: http://blog.programmableweb.com/2011/10/03/4000-web-apis-whats-hot-and-whats-next/

10. The New Web
Create an Architecture of Participation across
multiple brand name properties
Source: http://blog.programmableweb.com/2011/01/03/api-growth-doubles-in-2010-social-and-mobile-are-trends/

11. 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

12. New Requirements

13. API Store
• API discovery and
recommendation Build and Test • Upgrade notification
• Requirements matching • API monetization
• Review ratings and comments • Developer on-boarding • On-board new
• Funding gate consumers
• API integration
• Approval gate
Design Deploy
Common Environment Services
Identity Server
API
and Key API Registry Repositories
Governance
API Store Management
• Developer credential provisioning
API Store API Store API Store
Dashboards Back Office • API access provisioning
Front
• API meta-data storage
• Asset promotion and demotion

14. API Management Solution

15. Enterprise Application Development Environment
API
Developer
API API Development
Provisioning • Governance
and • Description
configuration
Enterprise
Application API • Collaboration Tools
DevOps Tooling Development Store
Environment
API
SVN / Versioning
Git Eclipse
Portfolio
Management API Management
Credential
Dashboards Vertical PaaS Management
• Operations • API
• Development • Domain Capabilities
• Tenant Configuration
• Monetization

16. Vertical Ecosystems

17. Vertical PaaS
Vertical Application 1 Vertical Application 2 Vertical Application 3
Personalization API
App Data App Data App Data
Tenant
App Source Code App Source Code App Source Code
App App App
Configuration Configuration Configuration
Vertical
Domain API Domain API
Domain Artifacts Domain Artifacts
Managed
Programming Languages
by PaaS
Frameworks
Containers
OS/Hypervisor
Hardware

18. 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

19. 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

20. 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”

21. 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

22. Business Drivers for Vertical PaaS
22
• 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

23. Beyond APIs:
“Your Business As A Service”
Users
Partners
Tenant Tenant Tenant Tenant
Apps Apps Apps Apps
Ecosystem Owner
PaaS / Stratos
API Management / API Store
Existing business systems as APIs

24. 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

25. 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

26. “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

27. 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

29. One Enterprise Platform wherever you need it:
WSO2 Carbon  WSO2 Stratos  WSO2 StratosLive
On Premise: In Private Cloud: As a Service in the Public
• In Production at Fortune • A single managed platform Cloud:
1000 companies • Elastic, Self-Service, Multi- • We manage, run and
• Handling 1bn tenant maintain your application
transactions/day • Accelerates your private platform
• The only modular open cloud beyond virtual • Complete Pay as you Use
source middleware stack machines to provide real • ESB-as-a-Service
• Everything you need to Enterprise Cloud Services • Governance-as-a-Service
build Enterprise • Use only what you need • Identity-as-a-Service
Applications • With appropriate SLAs and
• From Core Logic to Mobile simple monthly billing
Apps
• 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