Your SlideShare is downloading. ×
Stratos and PaaS for London Java Community
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Introducing the official SlideShare app

Stunning, full-screen experience for iPhone and Android

Text the download link to your phone

Standard text messaging rates apply

Stratos and PaaS for London Java Community

3,038
views

Published on

The presentation on WSO2 Stratos and PaaS I gave the London Java Community

The presentation on WSO2 Stratos and PaaS I gave the London Java Community

Published in: Technology

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
3,038
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
56
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • Tutorial: Platform as a service is exposed to its users as a familiar middleware service, but below the "surface," there are layers of cloud-specific technology that deliver the scalability, availability, elasticity and self-service that are essential to the cloud computing experience. Platform as a service is middleware "in the sky." Although offered as a service, its functional role remains the role of the middleware — platform, integration or other middleware type. Because there are different types of middleware offerings (application servers, integration brokers [ESBs], business process management suites [BPMSs], portal products, messaging products, etc.), each can also be delivered as a service. In some cases, these middleware services are delivered stand-alone as specialized PaaS services (StormMQ is a specialist messaging service). More often, the same cloud service provider offers multiple middleware services to meet the requirements of real-world projects (force.com includes services of a DBMS, an application server and an application development tool). Over time, most PaaS providers will aim to deliver a growing set of middleware functions. To be implemented as a cloud service, a PaaS service must not only deliver its middleware functionality, but also possess the features that make it cloud-worthy (the cloud performance foundation) and cloud-enabled (cloud behavior foundation). The cloud performance foundation is responsible for scalability and availability to match the potential demand of the global cloud user base. The cloud behavior foundation delivers resource sharing, multitenancy, elasticity, self-service and other characteristics expected of a cloud service. The common, shared development and management environments complete the picture of a well-designed PaaS platform, whether it offers only a few middleware services or is a comprehensive end-to-end PaaS.
  • Transcript

    • 1. Platform-as-a-Service and WSO2 Stratos Paul Fremantle CTO and Co-Founder www.wso2.com [email_address] #pzfreo
    • 2. Paul Fremantle
      • Working in Apache since 2002
      • Apache Member and Committer
      • CTO and Co-Founder of WSO2
      • VP, Apache Synapse
      • 10 years at IBM ending as STSM in WebSphere Development
        • Led the IBM Web Services Gateway team
      • I also play the Tin Whistle
      @tedleung
    • 3. Moore ’ s Law for Data
      • The amount of data online went from
        • 5 exabytes in 2002
        • 281 exabytes in 2009
      • Doubling every 15 months
      • You cannot deal with this data growth with the same applications
        • A reasonable conclusion is that the number of applications will double every 15 months too
    • 4. Cloud Native Attributes
      • http ://bit.ly/CloudNative
      • Core Attributes
        • Self-service
        • Multi-tenant
        • Distributed / Scalable
        • Elastically / Dynamically Scaled
        • Metered
      • Extended attributes
        • Incrementally Deployable and testable
        • Billed
        • Dynamically wired
    • 5. http://www.flickr.com/photos/ladymaggic/
    • 6. http://www.flickr.com/photos/jurvetson/
    • 7. Gartner Reference Model for Platform as a Service Hardware Integrated PaaS Platform Management, Monitoring, Governance, Provisioning System Infrastructure or System Infrastructure Services (IaaS) PaaS Service Offerings PaaS Technology Core Integrated PaaS Application Modeling, Design, Development, Maintenance, Life Cycle Management Applications PaaS IaaS SaaS Cloud Performance Foundation Cloud Value Foundation ( Shared Resources, Multitenancy, Self-Service, Elasticity, Real-Time Versioning, Metadata Management, Subscription/Use Billing) (In-Memory Computing, Grid/Massive Scale, Auto-Scaling, SLA Enforcement, Use Tracking, High Availability, Security, Data Integrity, Parallel Processing) Application Platform Integration Platform Business Process Management Platform Cloud Database Platform Other User Experience Platform
    • 8. Shared what?
      • Shared Nothing
      • Shared Hardware
      • Shared Database
      • Shared OS
      • Shared Container
      • Shared Everything
    • 9.  
    • 10. Central Limit Theorem
    • 11. Cloud Middleware Platform and PaaS
      • A PaaS requires an underlying software base
        • Cloud Middleware Platform (CMP), or
        • Cloud Enabled Application Platform (CEAP – Gartner)
        • “ Private PaaS” / On Premise PaaS
      • Not all PaaS have redistributable CMPs
      • The benefit of having a CMP is choice:
        • Run your own PaaS in a private cloud
        • More than one PaaS provider
      • Open PaaS / Open CMP fights lock-in
    • 12. Carbon and Stratos Single-tenant Multi-tenant On premise deployment WSO2 Carbon products WSO2 Stratos Cloud / Elastic deployment WSO2 Carbon Cloud Images WSO2 StratosLive Shared Codebase Open Source Apache License Open Development
    • 13. One Enterprise Platform wherever you need it:
      • 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
      • 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
    • 14. Stratos Overview
      • A full middleware platform available as a service, with self service
        • Fast provisioning
      • Based on OSGi
        • Modular, componentized, standard
      • Multi-tenant, Elastic, Metered and Billed
        • Effective and powerful
      • Available under the Apache License
        • Open Source, Open License, Open Development
    • 15. Stratos resources
      • Stratos SVN
        • http://svn.wso2.org/repos/wso2/trunk/stratos/
      • Stratos-dev list
        • https://mail.wso2.org/cgi-bin/mailman/listinfo/stratos-dev
      • Blog on how to build / install
        • http://yumani.blogspot.com/2011/06/setting-up-wso2-stratos-in-personal.html
    • 16. Stratos and StratosLive Timeline
      • Stratos is the code/product, StratosLive is the service
      • April 2010
        • Stratos alpha release
        • StratosLive alpha
      • November 2010
        • Stratos 1.0 Gold
        • StratosLive 1.0 beta
      • July 2011
        • Stratos 1.5.1
        • StratosLive GA
      © WSO2 2011
    • 17. StratosLive
      • 1.0 codebase Beta http://cloud.wso2.com
      • 1.5 codebase GA http://stratoslive.wso2.com
      • (warning we are just going live on Monday 18 th !)
    • 18. Installation options
      • 1. Full installation
        • Pre-reqs
          • IaaS – Eucalyptus, vmWare, Ubuntu or Amazon
          • MySQL & Perl & JVM
          • Ability to run a number of VMs (one per service)
      • 2. Laptop/Simple install
        • Pre-reqs
          • A machine with lots of memory (4Gb min, 8GB preferred)
          • JVM
          • MySQL & Perl
    • 19. Installation of Stratos 1.5.1 pack
      • Config mysql
        • max_allowed_packet = 16M
      • ulimit –n 65000
      • Unzip the distro
      • cd stratos
      • ./stratos-setup.pl
      • export STRATOS_DIR=`pwd`/deploy
      • cd deploy
      • ./stratos.sh start all
    • 20. Who are the players in the PaaS market?
      • Those without a Private PaaS
        • Force.com
        • Heroku
        • Google App Engine
        • Amazon Elastic Beanstalk
      • Those with a Private / Public PaaS
        • Tibco
        • Microsoft (nearly)
      • Those with an Open Private / Public PaaS
        • SpringSource CloudFoundry
        • WSO2 Stratos
    • 21. Available Services (low level)
      • Multi-tenancy
      • Deployment synchronizer
      • Elastic Load Balancer
        • tenant-aware
      • Tenant-aware identity manager
        • SAML2, OpenId, Oauth, XACML
      • Tenant Metering and Billing
      • Discovery
      • Logging
      • Configuration & Repository
      • Data-as-a-Service
      • Queueing-as-a-Service
      • Health Monitor
      • Private / Public Cloud bridging
    • 22. Every Service has a network API
      • All admin functions and all the low level services are available as SOAP APIs
        • Full SOAP support, REST in some cases
        • Always possible to bridge into REST using the ESB
      • Why?
        • Clear SOA design
          • Allow mashups, BPEL and ESB integration
        • Automated provisioning
        • Support hybrid multi-tenancy models for legacy software
    • 23. Available Services (mid-level)
      • Application Server
        • Webapp deployment
          • Multi-tenant deployment of Tomcat 7
        • Service Deployment
          • Axis2, JAXWS, POJO, Spring
        • Transaction Manager
        • SaaS deployment model
      • Portal Server
        • Based on the OpenSocial/Google Gadget spec
        • Gadget repository and strong personalization features
        • SAML2 and OpenId Single Sign-on
      • Data Services
      • Enterprise Service Bus
        • Full multi-tenant deployment of Apache Synapse
      • Governance Registry
        • Governance-as-a-Service model
    • 24. Available Services (high-level)
      • Business Process Manager
        • Full BPEL runtime in the cloud
        • Human Task support
      • Business Rules Server
      • Complex Event Processing
      • Business Activity Monitoring
    • 25. Case Studies (in progress)
      • System Integrator
        • Currently running Stratos for internal projects
        • Examining the use of Stratos for customer projects and SaaS
      • Home Loan Bank
        • WSO2 runs a private deployment of Stratos
        • Developer sandbox and test environment
        • Currently apps are then deployed internally in Carbon
      • Niche PaaS
        • Combination of cross tenant services / APIs
        • Allow each tenant to deploy / customise the logic
      • Mobile PaaS
        • Building a PaaS environment for a mobile telco
      • SaaS-enablement of legacy applications
    • 26. Futures
      • SLA management and Priority Execution
      • Better thread/CPU management and instrumentation
      • HDFS support
      • VM deployment
      • End-to-end development lifecycle integration (Maven, SVN, Hudson/Jenkins, Junit)
    • 27. Still time to Register! http://freo.me/mSBIOX
    • 28. Questions? http://www.flickr.com/photos/oberazzi/