• Save
NWCloud Cloud Track - A comparative analysis of the development experience across cloud strata
Upcoming SlideShare
Loading in...5
×

Like this? Share it with your network

Share

NWCloud Cloud Track - A comparative analysis of the development experience across cloud strata

  • 1,339 views
Uploaded on

NWCloud Cloud Track Session

NWCloud Cloud Track Session

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads

Views

Total Views
1,339
On Slideshare
1,336
From Embeds
3
Number of Embeds
1

Actions

Shares
Downloads
0
Comments
0
Likes
1

Embeds 3

http://www.slideshare.net 3

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
  • Comparative view of development experience across several cloud offerings Goal: help you know where to start, and what cloud layer is appropriate for the type of solution you are developing One target application: a simple blog Several development platforms
  • SaaS – wheel already been invented PaaS – “pure code”, just write your code, don’t worry about where to host it or how to configure the system IaaS – pretty much like a VM hosted “out there”, you own coding and System Configuration, but not physical maintenance or support
  • Apex based on Java, c-style syntax – easy for c# or java devs to pick up VisualForce – markup (like asp.net or jsp) Database – sObjects DTO/Table/Schema all wrapped up into one Built in test framework – requires 75% code coverage for a given test run to pass Tests must pass in order to be able to deploy to production Can’t do “full” TDD because files are saved (and compiled) one at a time Deployment is eeeeeasy Built in security, but can do federated authentication
  • Eclipse again!? You don’t *have* to use it, but I’m lazy. If you use a different IDE - /appengine-java-sdk/demos/new_project_template/ Google Web Toolkit – compile Java into JavaScript for rich-client web app Google App Engine – dev code for normal servlet-style app Data storage in App Engine Datastore – uses DataNucleus (either JDO or JPA) Write normal java servlets according to Java Servlet standard Debug using Eclipse plugin If you read the tutorial, there is lots of “if you’re not using Eclipse, then do this. Otherwise, it was done for you.” Most of the eclips functionality is also provided as ANT scripts This is cool – normal Java (almost). There is a JRE Class Whitelist, you can’t use classes from the JRE that aren’t on that list.
  • When you sign up you get [something] .appspot.com Eclipse again!? You don’t *have* to use it, but I’m lazy. If you use a different IDE - /appengine-java-sdk/demos/new_project_template/ Google Web Toolkit – compile Java into JavaScript for rich-client web app Google App Engine – dev code for normal servlet-style app Data storage in App Engine Datastore Write normal java servlets according to Java Servlet standard Debug using Eclipse plugin If you read the tutorial, there is lots of “if you’re not using Eclipse, then do this. Otherwise, it was done for you.” Most of the eclips functionality is also provided as ANT scripts
  • When you sign up you get [something] .appspot.com Eclipse again!? You don’t *have* to use it, but I’m lazy. If you use a different IDE - /appengine-java-sdk/demos/new_project_template/ Google Web Toolkit – compile Java into JavaScript for rich-client web app Google App Engine – dev code for normal servlet-style app Data storage in App Engine Datastore Write normal java servlets according to Java Servlet standard Debug using Eclipse plugin If you read the tutorial, there is lots of “if you’re not using Eclipse, then do this. Otherwise, it was done for you.” Most of the eclips functionality is also provided as ANT scripts

Transcript

  • 1. Coding in the Cloud A review of the development experience across cloud strata
  • 2. Eric Peterson Principal Consultant Centerstance Introduction
  • 3. Goal: a taste of development experience in several different cloud offerings. No fear! Review: SaaS – Blogger PaaS – Force.com, Google Apps IaaS – AWS EC2 Overview
  • 4.
    • SaaS – Software as a Service
      • Configuration vs. Coding
      • Usually customizing a solution for a known/solved problem.
    • PaaS – Platform as a Service
      • “ pure code”
      • Don’t have to worry as much about system configuration.
    • IaaS – Infrastructure as a Service
      • VMs hosted “somewhere”
      • You still own system configuration and coding
    Cloud Strata
  • 5.
    • Sign up
    • Configure
    • Done
    • No code!
    SaaS - Blogger
  • 6.
    • Proprietary language(s) – Apex, VisualForce
    • Eclipse IDE plugin for dev, testing, deployment
    • Dev locally
    • “ compile”, test in the cloud
    PaaS – Force.com
  • 7. PaaS – Force.com
  • 8. PaaS – Force.com Apex VisualForce SOQL
  • 9. PaaS – Force.com
  • 10. PaaS – Force.com
  • 11.
    • Java or Python
    • Eclipse IDE plugin for dev, testing, deployment
    • “ compile”/Dev/Test locally
    PaaS – Google App Engine
  • 12. PaaS – Google App Engine
  • 13. PaaS – Google App Engine JSP Java JDO
  • 14. PaaS – Google App Engine
  • 15.
    • Java, Python, .NET, PHP, Ruby, Caml, etc.
    • Pick your OS (Windows, Linux, Solaris)
    • Pick your IDE
    • Can Dev/test in the cloud or locally
    IaaS – Amazon EC2 with .NET
  • 16. IaaS – Amazon EC2 with .NET
  • 17. IaaS – Amazon EC2 with .NET ASP.NET C# SimpleDB
  • 18. IaaS – Amazon EC2 with .NET
  • 19.
    • SaaS – Software as a Service
      • Good if known problem/known solution
    • PaaS – Platform as a Service
      • Trade control for speed, multi-tenancy can be limiting
      • Cheap/free for simple Hello World apps
    • IaaS – Infrastructure as a Service
      • No Platform-provider “rules”
      • Exellent starting point to port “physical” apps to the cloud
      • Less abstract than developing in PaaS
    Conclusions
  • 20. Getting on the right path to the cloud with AWS 4/21 – Portland, OR http://bit.ly/cxBb2G Seattle AWS User Group Meeting 4/27 – Seattle, WA http://bit.ly/sawsugmar2010 Eric Peterson [email_address] www.centerstance.com centerstance.wordpress.com @centerstance Q&A