Cloud migration slides


Published on

Explore the challenges of migrating existing applications to a cloud infrastructure, then present proven strategies for mitigating the risks You'll learn how to:

- Prioritize application migration
- Plan for “big-blocks”
- Assess your existing applications' ‘fit’ for cloud
- Leverage a centralized development testing platform to align your business goals with coding decisions
- Create a cloud migration policy
- Use process to mitigate the risks associated with cloud migration

Published in: Technology
  • Be the first to comment

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

No notes for slide
  • Use well-defined componentsEasy to reuseEasy to testEasy to secure
  • Check cyclical (circular) dependencyRun metrics analysisStatic analysis to find high dependencies
  • Giant files (over xxx lines)Giant methods/functions (over xxx lines)Poor coverage can point to monolithic code
  • What is “global” in a service oriented context?Use static analysis to pin-point and remove global variables
  • Uncaught exceptions are more troublesome in a cloud infrastructureNull pointers can wreak havocWhat to do:Static for unhandled exceptions and nullsAuto-generation for nulls and unhandled runtime exceptions
  • Cloud migration slides

    1. 1. Migrating Applications to the CloudPrevent the Most Common Reasons for Failure Parasoft November 2012
    2. 2. Cloud “Migration”…What we see Stage Characterized SummaryRogue Experimentation  Against or before an internal mandate  Pure simplicity versus internal processes  Cool factorAd Hoc Fun with Virtualization  Leverage server virtualization in cloud  Only increases risk (and cost) due to duplicationTrial and Error Business Interest  Opportunity to deliver business value  In “Cloud we Trust…”Responsibility Service Level Agreement  Architecture analyzed  Business penalties palpable  Real refactoring / redesign starts
    3. 3. Major Cloud Application Considerations Infrastructure Architecture Monitoring Security Instrumentation Automation Latency Parallel Event-Driven Fault Tolerance Resource Consumption
    4. 4. Where To Start Create your policy Determine your basic desired architecture Align with a service provider that meets your business needs and realize that this will be a give and take Don’t remodel - rebuild
    5. 5. The old into the new UI database authentication computation legacy systemParasoft Proprietary and Confidential 5
    6. 6. Break it down  Plan out your components  Select the pieces to be reworked and peer-review the plan  Well designed components use API only  Public member fields are a no-noParasoft Proprietary and Confidential 6
    7. 7. Architectures Tips & Tricks  You want to be:  Parallelizable  Fault tolerant  Resource independentParasoft Proprietary and Confidential 7
    8. 8. Don’t Run in Circles Package A Package C Package BParasoft Proprietary and Confidential 8
    9. 9. No Monoliths in the Cloud Giant Files Giant FunctionsParasoft Proprietary and Confidential 9
    10. 10. Thinking GloballyParasoft Proprietary and Confidential 10
    11. 11. Be ExceptionalParasoft Proprietary and Confidential 11
    12. 12. Security is vital  Suddenly there are openings everywhere  Can’t rely on “it was checked elsewhere in the application”  Input validation covers wide swath of potential problems  OWASP Top 10  CWE Top 25Parasoft Proprietary and Confidential 12
    13. 13. Policy – Plan, Measure, Monitor  Decide what you’re going to allow and create specific policy  Measure / monitor  Flag violations as errors (policy enforcement)Parasoft Proprietary and Confidential 13
    14. 14. Questions  webinar@parasoft.comParasoft Proprietary and Confidential