The Three Stages of Cloud Adoption - RightScale Compute 2013
 

Like this? Share it with your network

Share

The Three Stages of Cloud Adoption - RightScale Compute 2013

on

  • 762 views

Speaker: James Staten - VP and Principal Analyst, Forrester Research ...

Speaker: James Staten - VP and Principal Analyst, Forrester Research

As a RightScale user you are clearly a leading adopter of cloud computing, but have you matured your use of the cloud to the point that you are fully exploiting the advantages it provides? Most cloud users aren’t. In this session, Forrester Research VP and Principal Analyst James Staten will help you understand how to move from a cloud user to an optimizer to a profit maker as you progress your understanding of cloud economics and evolve your application design and deployment practices.

Statistics

Views

Total Views
762
Views on SlideShare
762
Embed Views
0

Actions

Likes
1
Downloads
20
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • Elastic scale: Scaling down is key.How quickly can you turn off resources no longer in use?How small can you get your base footprint?Are you leveraging caching as much as you can?What you scale matters.Discrete component scaling drives efficiency.Autoscaling cloud services often costs less.Where traffic goes affects cost.When and where you do things matters.Some cloud services have off-peak pricing concepts.Some cloud services have better costs for certain services/uses.
  • This is a backup case we can analyze in case the audience doesn’t bring forth its own examples.
  • Why node.js:I/O bound for most interactionAggregation and manipulation of strings (e.g. JSON)Lots of persistant socket connectionsEasier for client side devs to grok
  •  3. Link to the legacy, then cut it loose. You can't abandon your in-house systems and all the legacy data but you can integrate it with the new models. Concentrate on this.           a. Where the new capabilities add new capability, make integration work but leave the legacy, legacy.           b. Use web services to extend the legacy rather than incur the expense of upgrading the legacy to try to make it relevant. Your users have moved on.           c. When the legacy is no longer in active use, cut it loose. Archive it and outsource it.
  • Opportunity to tease to Rich’s session 3. Link to the legacy, then cut it loose. You can't abandon your in-house systems and all the legacy data but you can integrate it with the new models. Concentrate on this.           a. Where the new capabilities add new capability, make integration work but leave the legacy, legacy.           b. Use web services to extend the legacy rather than incur the expense of upgrading the legacy to try to make it relevant. Your users have moved on.           c. When the legacy is no longer in active use, cut it loose. Archive it and outsource it.
  • This is where I reach out to the audience for their examples of how they are using the cloud or considering.

The Three Stages of Cloud Adoption - RightScale Compute 2013 Presentation Transcript

  • 1. © 2011 Forrester Research, Inc. Reproduction Prohibited1 © 2009 Forrester Research, Inc. Reproduction ProhibitedThe Three Stages of Cloud AdoptionJames Staten, Vice President, Principal Analyst
  • 2. © 2011 Forrester Research, Inc. Reproduction Prohibited2Scale out turns on thecloud.Scaling down turns on cloudeconomics.
  • 3. © 2011 Forrester Research, Inc. Reproduction Prohibited3The basics of cloud economics are clear• As demand rises, resources are added.• Requires apps to scale out• Load balancing governsElastic scale delivers just-in-time capacity.• No upfront payment• No commitment whether you use it or not• Costs aligned to usePay-per-use keeps costs low.• If you can build it, you can deploy it — fast.• API access drives use of automation.Self-service fuels productivity.
  • 4. © 2011 Forrester Research, Inc. Reproduction Prohibited4Turning cloud economics to your favor is the key• How quickly can you turn off resources no longer in use?• How small can you get your base footprint?• Are you leveraging caching as much as you can?Elastic scale: Scaling down is key.• Discrete component scaling drives efficiency.• Autoscaling cloud services often costs less.• Where traffic goes affects cost.What you scale matters.• Some cloud services have off-peak pricing concepts.• Some cloud services have better costs for certain services/uses.When and where you do things matters.
  • 5. © 2011 Forrester Research, Inc. Reproduction Prohibited5Three stages of cloud economics
  • 6. © 2011 Forrester Research, Inc. Reproduction Prohibited6Leverage the tools of cloud economics• When you do something• For how long you do itTime• Parts that act independentlyComponentization• What performs which actions• What economics it bringsService choice• What doesn’t consume storage• What doesn’t consume bandwidthCaching• How the code behaves• What the code does and how• Re-architect to activate cloud economicsCode optimization
  • 7. © 2011 Forrester Research, Inc. Reproduction Prohibited7How does Netflix use the cloud economics tools? Profitability up by cloud optimization Three key services– Movie encoding (movies/watt) Batch up encoding processes. Not time sensitive; can tap spot instances. Optimize storage formats to keep S3 costs low.– Video streaming service Store on S3, stream on multiple CDNs.– Optimize CDN choice by stream type and customer. Split customer login and device identification.– Log analysis — feeds BI system Leverage managed Hadoop from AWS. Re-architected BI from the ground up for bestcloud efficiencyKey tools used: Time Componentization Service choice Code optimizationFor more info, check out http://www.slideshare.net/adrianco/netflix-on-cloud-combined-slides-for-dev-and-ops andCloudscaling Blog (http://cloudscaling.com/blog/cloud-computing/cloud-innovators-netflix-strategy-reflects-google-philosophy).
  • 8. © 2011 Forrester Research, Inc. Reproduction Prohibited8NVoicePay taps the cloud to expand its marketAP Assist: Enable electronic payments for SMBs 90% of B2B invoice payments are still by check. Solution: SaaS-based vendor payment– $0.40 per payment; free vendor sign-up– Tight integration with key SMB systems (i.e., ADP for cardealers, First Data payment clearing-house) Rich but light client UI — Silverlight Needed to push new information to customers quickly– Needed elastic scalability, fast deploy, and iteration Forecasted huge transaction volumes Traditional hosting was more expensive — wouldn’t achieve scale.– Needed reusable cloud services to speed development Windows Azure AppFabric, storage, security services– Needed effectively 100% availability for ―Payment Dial Tone‖ The alternative was to build a massively expensive data center.“Building a mission-critical B2Bpayment network would have beennearly impossible without the lowcost, pay-as-you-go . . . WindowsAzure platform.”— Karla Friede, CEO, NVoicePayFor more info, check out NVoicePay website (http://nvoicepay.com/wp-content/uploads/2010/10/NVoicePay-MS-Case-Study.pdf).
  • 9. © 2011 Forrester Research, Inc. Reproduction Prohibited9How is NVoicePay leveraging cloud economics? What cloud economics tools are they using?– Time– Componentization– Service choice– Caching– Code optimizationFor more info, check out NVoicePay website (http://nvoicepay.com/wp-content/uploads/2010/10/NVoicePay-MS-Case-Study.pdf).
  • 10. © 2011 Forrester Research, Inc. Reproduction Prohibited10How NVoicePay activates cloud economicsIf it’s running, it’s cutting into profitability. Profits are pennies on each $0.40 transaction. Mission: Lower the cost of each payment.– Scale only when necessary. Scale only what needs to be scaled when necessary.– Chatter can cost you. Traffic flowing out of the cloud costs $$. Keep this traffic to a minimum using:– Caching, Batching, Rich-client actions.– Use cloud services to speed development. Windows Azure AppFabric Service Bus and Access Control Windows Azure Blob, Table, and Queue Storage Windows Azure Connect — secure extra cloud connectivity Silverlight client takes actions that ease cloud-premiseintegration.Key tools used: Time Componentization Service choice CachingFor more info, check out NVoicePay website (http://nvoicepay.com/wp-content/uploads/2010/10/NVoicePay-MS-Case-Study.pdf).
  • 11. © 2011 Forrester Research, Inc. Reproduction Prohibited11What code are we seeing in the cloud1: Forklift 2: Elastic 3: NativeRedeploy Apps ―As-is‖ to the cloudIAAS: EC2PAAS: CloudBees,Engineyard• Simple• Quick• Low- initial cost• Low elasticityLoad-balance, addOSS infrastructureIAAS: EC2PAAS: Azure• Let providerauto-scale• Somerefactoring• OPEX savingsDesigned with theInternet as the OSService composition• Facades• State migrates toedge of systems• Designed for failure,self healing• Continuousdeployment~70% ~20% ~10%
  • 12. © 2011 Forrester Research, Inc. Reproduction Prohibited12Why traditional applications struggle to run on truecloudsCloud Platforms Commodity, low HA HW Assume all resources will beshared Assume shared use of thenetwork and no performance SLA Can be run anywhere And instance can take over Are services to other elementsTraditional enterpriseapplications Assume stable, reliable HW Assume sole ownership of theresource Assume uninterrupted networkaccess Assume place Assume they are primary Have static interrelationships
  • 13. © 2011 Forrester Research, Inc. Reproduction Prohibited13App architectures must evolve to exploit scale outNovember 2012 “Don’t Move Your Apps To The Cloud ”
  • 14. © 2011 Forrester Research, Inc. Reproduction Prohibited14A Digest of Evernote Architecture 150M HTTP requests via ApacheThrift based Service API Multiple failover points 90+ shards of Debian/Java/Tomcat/Hibrnate/Ehcache/Stripes/GWT/MySQL VM images replicated to anotherserver User based sharding reduces noisyneighbor Imaging search indexing service isseparated into different endpoint Additional endpoint each have theirown scaleCloud Native Elements
  • 15. © 2011 Forrester Research, Inc. Reproduction Prohibited15What powers Instagram 0-14M users in year 1 Ubuntu running on EC2 AWS Elastic Load Balancer + Route 53 +3 NGINX instances Django(Python)+gunicorn for App servers Sharded PostgreSQL for Data Storage Photos stored to AWS S3 Cloudfront as CDN for acceleration Redis for feeds, Memcache Munin for monitoringCloud Native Elements
  • 16. © 2011 Forrester Research, Inc. Reproduction Prohibited16What powers Linked-in Mobile Node.js for high scale asynchronouseventing to clients Mobile server intermediatesbetween client and LinkedInplatform Screen API (JSON) – Domain API(Thrift) Nginx for higher throughput ofmessagesCloud Native ElementsiOSJS/HTML +NativeAndroidNativeMobile WebJS/HTMLOtherWrapJS/HTMLLoad BalancerNginx NginxNode JSServerNode JSServerLinkedIn Core PlatformMongoDBLoggingServerTrackingServerScreen-based REST APIDomain REST APIMobileServer
  • 17. © 2011 Forrester Research, Inc. Reproduction Prohibited17The NPR API architecture 43M pageviews in 2010 to 88M– 30M mobile Following a COPE strategy Appservers, Java, JSP, Struts MySQL as data managementlayer NoSQL XML repo for APIstaging PHP 5 /Linux in the APIhandling layer Memcache to accelreatereponsesCloud Native Elements
  • 18. © 2011 Forrester Research, Inc. Reproduction Prohibited18What about legacy apps?
  • 19. © 2011 Forrester Research, Inc. Reproduction Prohibited19Link to the legacy, then cut it looseWeb infrastructureLegacy
  • 20. © 2011 Forrester Research, Inc. Reproduction Prohibited20Recommendations• How does it generate revenue?• What actions are taken to get that revenue?• What components are involved?• What does the transaction flow cost?Understand the profitability profile of your cloud service.• Can you improve its scalability model?• How can its action timing be improved?• What alternative means (services, caching, reusablecomponents) can be leveraged?Analyze its performance profile.• Improve cloud coding practices through architectural adherence.• Architect in how to use the cloud economic tools — not thespecific uses.• Revisit this process often — as the cloud matures quickly.Bake the lessons learned into your cloud architecture.
  • 21. © 2011 Forrester Research, Inc. Reproduction Prohibited21What’s your cloud use case? What defines success for this service? What drives its profitability? What cloud economics tools are you using today? Discussion: How can you use them moreefficiently tomorrow? Cloud tools: Time Componentization Service choice Caching Code optimizationFor more info, check out NVoicePay website (http://nvoicepay.com/wp-content/uploads/2010/10/NVoicePay-MS-Case-Study.pdf).
  • 22. © 2009 Forrester Research, Inc. Reproduction ProhibitedThank youJames Staten+1 650.581.3824Twitter: Staten7www.forrester.com