Sonoa Cloud Services for Elasticity and Mobility


Published on

CloudCamp Haiti preso by Sam Ramji of Sonoa

Published in: Technology, Business
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Sonoa Cloud Services for Elasticity and Mobility

  1. 1. Cloud Services for Elasticity and Mobility<br />Sam Ramji, VP Strategy<br />Sonoa Systems<br />
  2. 2. In Brief<br />Cloud Services Overview<br />Pattern: Surge-driven Demand for Application Experiences<br />What Can We Do To Help Haiti?<br />What Can We Do To Help the next Haiti?<br />
  3. 3. Cloud Services Overview: Economics<br />Shifts are driven through business advantages offered:increased revenue, decreased costs, increased efficiency<br />Requires a new generation of infrastructureto mirror and extend web computing capabilities in a cloud computing world<br />APIs are replacing user interfaces as the next generation requires structured access to data and services<br />APIs are the core elements of the cloud economy<br />
  4. 4. Cloud Services Overview: Process<br />Business View<br />Technology View<br />Product Management<br />ITOperations<br />SoftwareDevelopment<br />BusinessDevelopment<br />concept<br />Fix the Economy<br />Advance the Internet<br />Drive faster innovation<br />Find new scalable profit models<br />Scalable innovation through remixing<br />Scalable revenue through Cloud services<br />Make services easier to build<br />pre-purchase<br />pre-purchase<br />Low cost transactions<br />Low cost customer acquisition<br />Make services easier to deploy<br />Make it easier to run the business<br />Make services easier to operate<br />1st<br />1st<br />Make it easier to be in compliance<br />Make services easier to predict<br />2nd<br />2nd<br />implementation<br />
  5. 5. Cloud Services Overview: Evolution<br />* Refers to mobile applications using APIs, not mobile websites<br />
  6. 6. Pattern: Surge-Driven Demand<br />PC<br />Netbook<br />Phone<br />Useful applications are available wherever the user is, with the right experience based on available compute infrastructure<br />This means custom clients using common APIs<br />APIs have to scale in order to meet demand<br />APIs need customization in order to accelerate delivery to different clients<br />
  7. 7. Pattern: Mobile Cloud Service Gateway<br /><ul><li>TV Guide on the iPhone
  8. 8. Used 3rd party API
  9. 9. 10x performance improvement through</li></ul>Mobile Mediation<br />Application Caching<br />Application Services<br /><ul><li>Scaled through cloud infrastructure through 500K users with unpredictable growth</li></li></ul><li>What Can We Do to Help Haiti?<br />Volunteers from our community to help onramp the IT leaders for the crisis<br />USAID<br />FEMA/Military<br />Crisis Commons <br />Let Aid Providers focus on the last mile and on the remote command centers<br />Containers solve these aspects of the problem<br />This is not a cloud issue, this is an access and domain specific knowledge issue<br />Utilize public infrastructure wherever possible<br />Drive awareness of existing infrastructure (internet and available services)<br />Establish a blessed registry of crisis APIs including documentation and best practices<br />Donate our infrastructure<br />Rackspace, Sonoa, IBM, Canonical, RightScale, and many more just on this webinar – we can each take action to coordinate our in-kind donations<br />
  10. 10. What Can We Do to Help the next Haiti?<br />Best practices<br />A community site to document the patterns and point to existing working applications and mashups<br />Cloud API registry for the Crisis Community<br />Thoughtful, documented place for known-good APIs<br />Donations from providers <br />Infrastructure: Amazon, Microsoft, Google, Rackspace<br />Application Engines: EngineYard/Heroku, Microsoft, Google<br />Management: RightScale, Sonoa<br />
  11. 11. THANK you<br />
  12. 12. Core Customer Scenarios<br />Mobile Gateway<br />APIGateway<br />FeedGateway<br />Cloudburst<br />Gateway<br />REST and SOAP APIs consumed by mobile apps<br />REST and SOAP APIs published and/or consumed<br />Feeds published at scale to content consumers<br />Public cloud used to “outburst” private computation<br />Mobile devices drive traffic and have special requirements<br />Secured access required to enable “private cloud” computing<br />Visibility, control of usage; large customers require customization<br />Dynamic content delivered through channels with 1:1 requirements<br />
  13. 13. Cloud Gateway<br /><ul><li>Authentication and authorization for all requests
  14. 14. Secure channel and confidential data masked out
  15. 15. Dashboard of usage
  16. 16. Cloud federation</li></li></ul><li>Customer infrastructure and applications<br />Customer Cloud Environment<br />Cloud Infrastructure Platform<br />Cloud Service Broker Appliance<br />
  17. 17. Customer infrastructure and applications<br />CloudInfrastructure Platform<br />Cloud-based Cloud Service Broker<br />Customer<br />Datacenter<br />
  18. 18. Cloud Service Controller as a Service<br />Customer infrastructure and applications<br />Cloud Infrastructure Platform<br />
  19. 19. Customers we’ve learned from<br />
  20. 20. Problem<br />Business<br />Technology<br />Web architectures do not support the new demand patterns and security models needed for cloud services<br />Companies are racing their competition to win in the cloud<br />After early successes, they are failing due to lack of visibility, control, and scalability<br />Cannot inspect, route, manage, and secure communications at the cloud layer<br />Business development is held back by lack of technical agility<br />Coding rather than configuration used to modify and evolve cloud services<br />Impact<br />Lost revenue<br />Customer dissatisfaction Compliance penalties<br />Impact<br />Cost overrunsPoor performance/SLA failures Business disruption<br />