CloudCamp Haiti preso by Sam Ramji of Sonoa

1. Cloud Services for Elasticity and Mobility Sam Ramji, VP Strategy Sonoa Systems

2. In Brief Cloud Services Overview Pattern: Surge-driven Demand for Application Experiences What Can We Do To Help Haiti? What Can We Do To Help the next Haiti?

3. Cloud Services Overview: Economics Shifts are driven through business advantages offered:increased revenue, decreased costs, increased efficiency Requires a new generation of infrastructureto mirror and extend web computing capabilities in a cloud computing world APIs are replacing user interfaces as the next generation requires structured access to data and services APIs are the core elements of the cloud economy

4. Cloud Services Overview: Process Business View Technology View Product Management ITOperations SoftwareDevelopment BusinessDevelopment concept Fix the Economy Advance the Internet Drive faster innovation Find new scalable profit models Scalable innovation through remixing Scalable revenue through Cloud services Make services easier to build pre-purchase pre-purchase Low cost transactions Low cost customer acquisition Make services easier to deploy Make it easier to run the business Make services easier to operate 1st 1st Make it easier to be in compliance Make services easier to predict 2nd 2nd implementation

5. Cloud Services Overview: Evolution * Refers to mobile applications using APIs, not mobile websites

6. Pattern: Surge-Driven Demand PC Netbook Phone Useful applications are available wherever the user is, with the right experience based on available compute infrastructure This means custom clients using common APIs APIs have to scale in order to meet demand APIs need customization in order to accelerate delivery to different clients

8. Used 3rd party API

10. What Can We Do to Help the next Haiti? Best practices A community site to document the patterns and point to existing working applications and mashups Cloud API registry for the Crisis Community Thoughtful, documented place for known-good APIs Donations from providers Infrastructure: Amazon, Microsoft, Google, Rackspace Application Engines: EngineYard/Heroku, Microsoft, Google Management: RightScale, Sonoa

11. THANK you

12. Core Customer Scenarios Mobile Gateway APIGateway FeedGateway Cloudburst Gateway REST and SOAP APIs consumed by mobile apps REST and SOAP APIs published and/or consumed Feeds published at scale to content consumers Public cloud used to “outburst” private computation Mobile devices drive traffic and have special requirements Secured access required to enable “private cloud” computing Visibility, control of usage; large customers require customization Dynamic content delivered through channels with 1:1 requirements

14. Secure channel and confidential data masked out

15. Dashboard of usage

17. Customer infrastructure and applications CloudInfrastructure Platform Cloud-based Cloud Service Broker Customer Datacenter

18. Cloud Service Controller as a Service Customer infrastructure and applications Cloud Infrastructure Platform

19. Customers we’ve learned from

20. Problem Business Technology Web architectures do not support the new demand patterns and security models needed for cloud services Companies are racing their competition to win in the cloud After early successes, they are failing due to lack of visibility, control, and scalability Cannot inspect, route, manage, and secure communications at the cloud layer Business development is held back by lack of technical agility Coding rather than configuration used to modify and evolve cloud services Impact Lost revenue Customer dissatisfaction Compliance penalties Impact Cost overrunsPoor performance/SLA failures Business disruption