Building out a private Platform-as-a-Service is becoming increasingly important to organizations. Many organizations see the benefits of cloud architecture and cloud services, but they have legal or organizational issues that mean they cannot utilize a pure public PaaS.
Stratos is a Platform-as-a-Service foundation product that enables organizations to build their own PaaS: whether it is within the datacentre, or in an existing cloud environment such as Amazon or Rackspace, or in any combination of the two. Stratos layers on top of existing Infrastructure Clouds such as OpenStack, vmWare vSphere, Amazon or Rackspace and provides a more developer focused experience. Stratos 2.0 is a major update that now supports polyglot environments including PHP, MySQL, and can be extended to support multiple models.
This workshop will show how Stratos can be installed, configured and used to provide a multi-tenant PaaS. Using demos on Amazon and local systems we will demonstrate the benefits of Stratos and PaaS in a private, hybrid or public cloud environment. The session will cover a number of areas including:
Multi-tenancy and MT models
Elastic Load Balancing
IaaS configuration and working across heterogeneous IaaSes including OpenStack, vmWare and Amazon
Plugging in different runtimes and the Cartridge model
How development and App Factory fit into the Stratos model
The workshop is aimed at cloud architects and developers interested in PaaS
|Chris Haddad, VP, Technology Evangelism
Chris works closely with developers, architects, and C-level executives, as well as WSO2's engineering team to increase WSO2 middleware technology adoption, enhance the Carbon and Stratos platforms, and maximize customer value. Previously, Chris led research teams at Burton Group and Gartner advising Fortune 500 enterprise organizations and technology infrastructure vendors on adoption strategies, architecture, product selection, governance, and organizational alignment. His team advanced best practices in PaaS, cloud application architecture patterns, SOA, and middleware. Prior to these roles, Chris focused on creating infrastructure frameworks, establishing repeatable development methodologies, contributing to open source frameworks, and delivering SaaS and Internet applications.