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
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
Notas do Editor
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
