The Pragmatic Cloud - for developers
Upcoming SlideShare
Loading in...5

Like this? Share it with your network


The Pragmatic Cloud - for developers



See recording here: ...

See recording here:

In the IT industry 2009 was apex of cloud promises and hype. The early, now cliché successes captured everyone’s attention and many vendors turned on a dime to deliver something – anything – with the word cloud in it. At the same time, the aging hype-silos of development like Agile development, rails, open source, and Java were cut back on their meal-rations unless they could connect with “cloud.” We’re hardly “done” with the cloud, but there are now endless deployment options, taxonomies, technologies, and distractions that are more smoke filled rat-holes than clouds. This talk deals with the state of things now and how you can take start pragmatically getting along with things in the current, cloud-injected development-scape.



Total Views
Views on SlideShare
Embed Views



1 Embed 11 11



Upload Details

Uploaded via as Adobe PDF

Usage Rights

CC Attribution-NonCommercial-ShareAlike LicenseCC Attribution-NonCommercial-ShareAlike LicenseCC Attribution-NonCommercial-ShareAlike License

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
Post Comment
Edit your comment

The Pragmatic Cloud - for developers Presentation Transcript

  • 1. The Pragmatic Cloud what development should care about Michael Coté, RedMonk @cote 1
  • 2. conclusions • Happier users with better applications - it’s not just about the software anymore • Thus far, most cloud-talk is operations focused • Development should start taking advantage of cloud technologies, responsibilities • Agile is a good start 2
  • 3. what is “cloud”? From William Vambenepe (@vambenepe) 3
  • 4. burgers & aaSes • SaaS, PaaS, IaaS - application, middleware, servers • Public or private • Amazon and everyone else • Usually: virtualization, model-driven automation, web apps, dev/ops 4
  • 5. things to point at • IaaS - Amazon EC2, S3, etc. • PaaS -, Microsoft Azure, IPP, Heroku • SaaS: SalesForce, Zoho, Google Apps, Paglo (Citrix), 5
  • 6. for users • SaaS - Google Apps, Salesforce, etc. • Business apps that behave like consumer web apps - better applications • Lower cost & faster delivery • Remote control for the cloud 6
  • 7. for operations • “Cloud” - moving infrastructure off premise • “Private cloud” - automating, virtualizing, self- service • Focus on infrastructure, not applications 7
  • 8. for developers • Becoming ops friendly - or subversive if you dare • Using cloud tools & practices to deliver applications • Getting closer to the user with faster delivery 8
  • 9. making users happy • Face it: most IT is terrible, boring, & complex “The computer is a moron.” • Continually simplifying -Peter Drucker • Lusting for cheap feedback 9
  • 10. less to manage • This probably means delivering as a SaaS • Perhaps with a PaaS - lockin risks • Cloud-friendly, if needed 10
  • 11. “apps” vs. “applications” “What we are looking to do is find other small areas that we can build a nice small app that’s done really well that can help hundreds of thousands of the QuickBooks millions.” -Brian Sweat, Product Manager at Alterity, Inc. Flexible Marketplaces User & & Expectations Cheap Feature delivery 11
  • 12. beyond tracking suffering “I can actually look at [a feature] and say, ‘nobody uses feature X.’ It's not even being looked at. And it really helps us shape the future of the app which, on a desktop product, we don't have a lot of data like that.” -Brian Sweat, Product Manager at Alterity, Inc. User Aggregate Feature analytics analytics analytics 12
  • 13. operations as bottle-neck • While developers have been delivering faster, operations has used process as armor • “Change management” means “preventing change” • But, they can’t be blamed - they need help! 13
  • 14. making friends with ops • Learn what/how operations people talk & worry about • Service desks, automation, service catalogs, SLAs, provisioning • Know their ivory tower & their muck 14
  • 15. developing for the cloud • Application geared towards automated delivery • Quick and easy to configure • Development must program operations - modeling, instrumenting • The window test 15
  • 16. “operations as code” Puppet, Chef, PowerShell 16
  • 17. “fully Automated Provisioning” * Capistrano One Orchestration Application Service ControlTier Deployment Fabric vendor’s Func take Provisioning Activity BCFG cfengine System Configuration Chef Configuration Puppet SmartFrog OS Install or Cloud: AWS* Cobbler Cloud or VM Bootstrapping OS Eucalyptus Jumpstart Image Install Kickstart OpenNebula Launch OpenQRM VMware* (*Not Open Source) From 17
  • 18. a tool: cloud labs • Self-service sysadmin • As with virtualization, dev & QA are early frontiers • Build-farms, no IT hassle • Provisioning vs. Configuration 18
  • 19. The Crazy aaS Dream One day, the development team will complete the iteration Every story works, and the app is shippable Minutes after the review meeting, operations clicks a button, & the users start using the new features 19
  • 20. Thank you! License Contact Michael Coté 512.795.4307 20
  • 21. Credits & Co. • Cloud model madness - • Larry quote: • Burger, CC-BY: • Woman “user”: • Operations guy: • Crazy wiring: • Chef screenshot: John Willis ( • PowerShell screenshot: • Brian Sweat quotes: • Fully automated provisioning: 21