Beyond Economics - Cloud as a Business Enabler
1 like•974 views
The document discusses the evolution of cloud computing and platform as a service (PaaS). It describes how PaaS has emerged from infrastructure as a service (IaaS) providers expanding their offerings and from software as a service (SaaS) providers exposing more customizable platforms. The document advocates developing and running a custom PaaS to gain control over the development environment and better utilize resources. It presents an example of how a PaaS could be built by integrating existing systems through an enterprise service bus and business process server.
Beyond Economics - Cloud as a Business Enabler
- 1. Cloud as a Business Enabler Moving Beyond Economics Open Source Junction 3 Paul Fremantle CTO, WSO2 [email protected] @pzfreo #wso2 #qconlondon © WSO2 2012 @pzfreo #wso2
- 2. © WSO2 2012 @pzfreo #wso2
- 3. Elasticity 0à1 © WSO2 2012 @pzfreo #wso2
- 4. ? © WSO2 2012 @pzfreo #wso2
- 5. Central Limit Theorem In probability theory, the central limit theorem (CLT) states that the mean of a sufficiently large number of independent random variables, each with finite mean and variance, will be approximately normally distributed. © WSO2 2012 @pzfreo #wso2
- 6. Cloud Economics • Public Cloud economy is based on the Central Limit Theorem • For Private Clouds the CLT sucks* * Apologies for using technical jargon © WSO2 2012 @pzfreo #wso2 6
- 7. Moore’s Law for Data • The amount of data online went from – 5 exabytes in 2002 – 281 exabytes in 2009 • Doubled 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 © WSO2 2012 @pzfreo #wso2
- 8. Application Development is yet to have its Industrial Revolution The Industrial Revolution was driven by key technologies: • Componentization – making tools and products from re-usable, standardized components. • Which relied on standardized metrics/measures so that components could fit together • Factories – A large clean space where multiple parts of the production process could share light, power and management to create consistency and governance. • The IT industry is only just now reaching its industrial revolution. Open Standards are the metrics, Modularity Code and SOA are the componentization. Platform-as-a-Service is the Factory. © WSO2 2012 @pzfreo #wso2
- 9. Enterprise Application Development Challenges • Project Infrastructure takes too long to setup • Too many projects fall through the cracks and use non- standard infrastructure, build, governance • Projects use too many different unknown or unapproved libraries, frameworks, etc • No clear idea of which projects are at which stage • Few or no metrics on code quality, test coverage, re-use • Little automated build or test • Best practices are not applied everywhere • Infrastructure takes too long to setup © WSO2 2012 @pzfreo #wso2
- 10. What is Cloud? • Depends who you are – My daughter: iCloud (her music in the cloud) – My mum: gmail (her email in the cloud) – My VP sales: Salesforce (his prospects in the cloud) – Sysadmin: Amazon/Rackspace/etc (his infrastructure in the cloud) – *: what you care about, self-provisioned, managed, metered and paid per use, in the cloud © WSO2 2012 @pzfreo #wso2 10
- 11. Cloud Native • Distributed/Dynamically Wired (works properly in the cloud) • Supports deploying in a dynamically sized cluster • Finds services across applications even when they move • Elastic (Uses the cloud efficiently) • Scales up and down as needed • Works with the underlying IaaS • Multi-tenant (Only costs when you use it) • Virtual isolated instances with near zero incremental cost • Implies you have a proper identity model • Self-service (in the hands of users) • De-centralized creation and management of tenants • Automated Governance across tenants • Granularly Billed and Metered (pay for just what you use) • Allocate costs to exactly who uses them • Incrementally Deployed and Tested (seamless live upgrades) • Supports continuous update, side-by-side operation, in-place testing and incremental production © WSO2 2012 @pzfreo #wso2
- 12. http://www.flickr.com/photos/ladymaggic/ © WSO2 2012 @pzfreo #wso2
- 13. http://www.flickr.com/photos/jurvetson/ © WSO2 2012 @pzfreo #wso2
- 14. PaaS Software as a Service Custom- Dev Platform as a Service ization Ops Infrastructure as a Service © WSO2 2012 @pzfreo #wso2 14
- 15. Evolving from different strands • Evolving “upwards” from IaaS – Amazon • Queuing, Mail, Notification/Events, Databases, Workflow, etc • Elastic BeanStalk • Evolving “downwards” from SaaS – Force.com – a place to host additional per-tenant logic – Google App Engine • Evolving “sideways” from middleware Platforms – WSO2, Tibco, vmWare, Oracle, IBM © WSO2 2012 @pzfreo #wso2
- 16. Amazon’s move to become a PaaS • Simple Queue Service • Relational Data Service • Simple Notification Service • Simple Workflow Service • Mail Service • Elastic Beanstalk © WSO2 2012 @pzfreo #wso2
- 17. Lock In © WSO2 2012 @pzfreo #wso2
- 18. StratosLive – http://stratoslive.wso2.com © WSO2 2012 @pzfreo #wso2 18
- 19. How do you deal with multi- tenancy? • Separate hardware, separate VMs, separate containers, separate “zones” • Different techniques for different systems: – Java: thread isolation, classloaders, shared classloaders – Linux: LXC, chroot – MySQL, Oracle: create a DB per tenant – Cassandra: keyspace isolation © WSO2 2012 @pzfreo #wso2
- 20. Run your own PaaS? • Large enterprise with different groups of developers – Consistent runtime internally – Better utilization • Even more interesting: – Domain-specific PaaS – Vertical PaaS – Your Business As A Service © WSO2 2012 @pzfreo #wso2
- 21. Vertical / Domain PaaS Ecosystem Owner Partners Users aka “Your Business As A Service” Tenant Tenant Tenant Tenant Apps Apps Apps Apps PaaS API Management / API Store Existing business systems as APIs © WSO2 2012 @pzfreo #wso2
- 22. How does it work? • A set of integrated systems – e.g.: – Redmine, project management – SVN, Git – JIRA – Identity Server – Governance Registry – Maven – Stratos • Integrated using ESB and Business Process Server – Each system is connected via ESB – Simple BPEL workflows orchestrate activities © WSO2 2012 @pzfreo #wso2
- 23. © WSO2 2012 @pzfreo #wso2
- 24. Questions? © WSO2 2012 @pzfreo #wso2