Interop 2011 - Scaling Platform As A Service

2,768 views
2,659 views

Published on

Most enterprise cloud adoption has relied on virtual machines and infrastructure as a service. However, there is a lot to love about the other approach to clouds—platform as a service. In a PaaS model, you worry about your code, and the systems take care of the rest. True Platform-as-a-Service not only reduces the cost of hardware infrastructure, but also reduces the complexity of the software stack that runs on it. PaaS promises to trim development and deployment time from months and years to days and weeks, but what are the signs of a true PaaS powerhouse? Is it simply free of servers or software to manage? Does it provide automatic upgrades and elasticity? Can you develop in multiple languages and across multiple device platforms? Many informed analysts think PaaS is the inevitable consequence of true utility computing. In this session, Patrick Chanezon of VMWare explains why PaaS may be the future of the enterprise.

Published in: Technology
0 Comments
4 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
2,768
On SlideShare
0
From Embeds
0
Number of Embeds
8
Actions
Shares
0
Downloads
73
Comments
0
Likes
4
Embeds 0
No embeds

No notes for slide

Interop 2011 - Scaling Platform As A Service

  1. 1. Beyond Virtual Machines Scaling PaaSPatrick ChanezonSenior DirectorDeveloper Relationschanezonp@vmware.comhttp://twitter.com/chanezon 2Monday, October 3, 11
  2. 2. P@ in a nutshell • French, based in San Francisco • Senior Director, Developer Relations,VMware • Software Plumber, API guy, mix of Enterprise and Consumer • 18 years writing software, backend guy with a taste for javascript • 2 y Accenture (Notes guru), 3 y Netscape/AOL (Servers, Portals), 5 y Sun (ecommerce, blogs, Portals, feeds, open source) • 6 years at Google, API guy (first hired, helped start the team) • Adwords, Checkout, Social, HTML5, CloudMonday, October 3, 11
  3. 3. Predictions “The future is already here — its just not very evenly distributed” William Gibson 3Monday, October 3, 11
  4. 4. Predictions My daugter Charlotte 4Monday, October 3, 11
  5. 5. Architecture Changes: 60’s MainframeMonday, October 3, 11
  6. 6. Architecture Changes: 80’s Client-ServerMonday, October 3, 11
  7. 7. Architecture Changes: 90’s WebMonday, October 3, 11
  8. 8. Architecture Changes: 2010’s Cloud, HTML5, MobileMonday, October 3, 11
  9. 9. Back to Client Server: Groovy Baby! 9Monday, October 3, 11
  10. 10. Hype warning: Cloudy, with a chance of real innovation Source: Gartner (August 2009) 10Monday, October 3, 11
  11. 11. What is Cloud Computing? Cloud According to my daughter Eliette 11Monday, October 3, 11
  12. 12. Cloud Stack - Classic Pyramid Software As A Service Platform As A Service Infrastructure As A Service 12Monday, October 3, 11
  13. 13. Cloud Stack - By Number Software As A Service Platform As A Service Infrastructure As A Service 13Monday, October 3, 11
  14. 14. Cloud Stack - By Value Software As A Service Platform As A Service Infrastructure As A Service 14Monday, October 3, 11
  15. 15. Cloud Stack - Neutral Software As A Service Platform As A Service Infrastructure As A Service 15Monday, October 3, 11
  16. 16. Cloud Stack - History § What does cloud mean, 4 main angles • Software 1994 Netscape • Infrastructure 2002 Amazon AWS • Platform 2008 Google • Development now! § Industrialization of hardware and software infrastructure • like electricity beginning of 20th century, cf The Big Switch, Nick Carr § But software development itself is moving towards craftmanship 16Monday, October 3, 11
  17. 17. Crossing the Chasm § Build the whole product § Cloud getting mainstream: Apple iCloud § Opportunities and risks § Ecosystems, various platforms Picture from Wikimedia Foundation http://en.wikipedia.org/wiki/File:Technology-Adoption-Lifecycle.png 17Monday, October 3, 11
  18. 18. Cloud started at Consumer websites solving their needs • Google, Amazon, Yahoo, Facebook, Twitter • Large Data Sets • Storage Capacity growing faster than Moore’s Law • Fast Networks • Horizontal -> Vertical scalability • Open Source Software • Virtualization • Cloud is a productization of these infrastructures • Public Clouds Services: Google, Amazon • Open Source Software: Hadoop, Eucalyptus, Cloud FoundryMonday, October 3, 11
  19. 19. IaaS/Virtualization getting mainstream § AWS, Joyent, Rackspace,... § Open Source projects: OpenStack, DeltaCloud, Eucalyptus § Standardization? DTMF § Inside the Firewall, Virtualization: VMware, Microsoft, Xen, KVM § Easy to provision, manage instance...BUT § Still need to manage backups, software stacks, monitor, upgrades 19Monday, October 3, 11
  20. 20. With Infrastructure, you still need to build your own platform § Need to build a distributed platform on top of you infrastructure § Story of the AWS meltdown from last summer • http://blog.reddit.com/2011/03/why-reddit-was-down-for-6-of-last-24.html • http://www.readwriteweb.com/cloud/2010/12/chaos-monkey-how-netflix- uses.php • http://news.ycombinator.com/item?id=2477296 • http://stu.mp/2011/04/the-cloud-is-not-a-silver-bullet.html § Twilio, Smugmug, SimpleGeo survived it because they built their own distributed platform on top of IaaS § Enterprise customers want to consider Infrastructure like CDNs • Multi Cloud usage • Based on Open Source de facto standards, or full standards whenever that happens 20Monday, October 3, 11
  21. 21. Platform Example: Google Ap Engine Datastore Layers Complex Entity Group Queries on Key range Get and set queries Transactions properties scan by key Datastore ✓ ✓ ✓ ✓ ✓ Megastore ✓ ✓ ✓ ✓ Bigtable ✓ ✓ 21Monday, October 3, 11
  22. 22. Megastore API § “Give me all rows where the column ‘name’ equals ‘ikai’” § “Transactionally write an update to this group of entities” § “Do a cross datacenter write of this data such that reads will be strongly consistent” (High Replication Datastore) § Megastore paper: http://www.cidrdb.org/cidr2011/Papers/ CIDR11_Paper32.pdf 22Monday, October 3, 11
  23. 23. Platforms § Web stack, nosql, sql § Google App Engine, Joyent, Heroku, Stax (Cloudbees), Amazon elastic beanstalk, Microsoft Azure, AppFog § Single or a few languages, services § Start of Multi language Polyglot platforms § Enabler for Agile Developers -> Create Business value faster § Lack of standards: risk, vendor lock-in § Enterprise needs: • Control, customizability • Private/Hybrid Cloud • Avoid lock-in 23Monday, October 3, 11
  24. 24. Main Risk: Lock-In Welcome to the hotel california Such a lovely place Such a lovely face Plenty of room at the hotel california Any time of year, you can find it here Last thing I remember, I was Running for the door I had to find the passage back To the place I was before ’relax,’ said the night man, We are programmed to receive. You can checkout any time you like, But you can never leave! 24Monday, October 3, 11
  25. 25. Cloud Foundry § Cloud Foundry Open PaaS • Open Source: Apache 2 Licensed • multi language/frameworks • multi services • multi cloud 25Monday, October 3, 11
  26. 26. Open Source Advantage § http://code.google.com/p/googleappengine/issues/detail?id=13 • https://github.com/cloudfoundry/vcap/pull/25 26Monday, October 3, 11
  27. 27. Fail often, fail quickly, and learnMonday, October 3, 11
  28. 28. Fail often, fail quickly, and learn • At Google Risk taking/Experimentation is encouraged • http://blog.red-bean.com/sussman/?p=96 “Do not be afraid of day-to-day failures — learn from them. (As they say at Google, “don’t run from failure — fail often, fail quickly, and learn.”) Cherish your history, both the successes and mistakes. All of these behaviors are the way to get better at programming. If you don’t follow them, you’re cheating your own personal development.” Ben Collins-Sussman (Subversion, code.google.com)Monday, October 3, 11
  29. 29. Agile Development ProcessesMonday, October 3, 11
  30. 30. Cultural Drivers: Agility • Waterfall -> Agile methodologies • Cloud enables an Agile culture, driver for innovation 1 2 http://www.yourdomain.com/Monday, October 3, 11
  31. 31. Agile Development Processes • Influences from XP, Agile, Scrum • Code reviews • Test Driven Development: Testing on the Toilets program and blog • Many internal development tools: Mondrian recently open sourced • Changed the meaning of beta • Teams co-located: 3-15 people, 4/cubicle, all close to each other • International offices: manage whole projects, avoid coordination costsMonday, October 3, 11
  32. 32. Agility as a survival skill § Software is becoming like fashion § Phone apps, social apps, short lifetime, fast lifecycles § Ab testing § Clay shirky situational apps § Kent Beck, Usenix 2011 Talk change in software process when frequency grows § Cloud is a powerful driver for agility § Scalability is built in the platforms § Can iterate faster § Focus on design 32Monday, October 3, 11
  33. 33. Chaos of creativity in developer Frameworks and Tools § Proliferation of languages and frameworks § Spring, Rails, Grails, Django § “Pythons has more webframeworks than language keywords” § Javascript, Python, PHP, Java, Groovy, Scala, Clojure, Go § Gosling, vm is important, not the language § Ability to create DSL important, cf Book § Fragmentation of communities § Chaotic Darwinian period, fun for the curious, deadly for the ossified § Online services replacing a lot of software § Mashups, Weaving services together § Pick your battles, choose what you need to build yourself to add value 33Monday, October 3, 11
  34. 34. Cloud for Developers: the true path is PaaS! 34Monday, October 3, 11
  35. 35. Books / Articles § Nick Carr, The Big Switch § Eric Raymond, The Art of Unix Programming § Weinberg, Psychology of Computer Programming § Wes python book § Mark html5 book § Kent Beck XP § Hunt, Thomas, The Pragmatic Programmer § Ade Oshineye, Apprenticeship Patterns § Matt Cutts Ignite Talk IO 2011, Trying different things § Josh Bloch talk about api design § Larry and Sergey, Anatomy of a Search Engine § Rob Pike, The Practice of Programming 35Monday, October 3, 11
  36. 36. Papers / Talks § Simon Wardley, Oscon 09 “Cloud - Why IT Matters” § Tim O’Reilly article on internet os § Peter Deutsch’s 8 Fallacies of Distributed Computing § Brewer’s CAP Theorem § Gregor Hohpe’s Starbucks Does Not Use Two-Phase Commit § Stuff I tag http://www.delicious.com/chanezon/ § My previous Talks http://www.slideshare.net/chanezon § My list of favorite books http://www.chanezon.com/pat/soft_books.html 36Monday, October 3, 11
  37. 37. Q&A 37Monday, October 3, 11
  38. 38. Acknowledgement § Drawings from my daughters Eliette & Charlotte § Cover picture from Ansel Adams 38Monday, October 3, 11

×