Se ha denunciado esta presentación.
Utilizamos tu perfil de LinkedIn y tus datos de actividad para personalizar los anuncios y mostrarte publicidad más relevante. Puedes cambiar tus preferencias de publicidad en cualquier momento.

Migrating Your Apps to the Cloud: How to do it and What to Avoid

254 visualizaciones

Publicado el

Migrating your applications to the cloud can be a harrowing journey, one fraught with complexity and uncertainty. What’s required to succeed, above and beyond the right platform, are the right set of people, equipped with modern practices, to build and run cloud native applications with confidence.

Join Allison and Tom, from Pivotal's Application Transformation (AppTx) team, as they discuss what common problems arise when teams try to get their apps on the platform and the AppTx team approach to solving them.

Whether you have purchased PCF (Pivotal Cloud Foundry) or are of a mind to move your legacy applications to the cloud this webinar will help you understand:

● Why it’s imperative to have a small team dedicated to the application portfolio
● When to re-platform, modernize or rewrite an application
● Strategies to address the most common issues we see

Speakers:
Allison Willams, Pivotal Senior Solutions Architect
Tom Collings, Pivotal Advisory Solutions Architect

Publicado en: Tecnología
  • How to start a wildly profitable 7 figure marketing business and get your first commission check tonight, click here ■■■ http://ishbv.com/j1r2c/pdf
       Responder 
    ¿Estás seguro?    No
    Tu mensaje aparecerá aquí
  • Tired of being scammed? Take advantage of a program that, actually makes you money! ★★★ https://tinyurl.com/y4urott2
       Responder 
    ¿Estás seguro?    No
    Tu mensaje aparecerá aquí

Migrating Your Apps to the Cloud: How to do it and What to Avoid

  1. 1. © Copyright 2018 Pivotal Software, Inc. All rights Reserved. Version 1.0 Migrating Your Apps to the Cloud: How to Do It & What to Avoid Tom Collings, Advisory Solutions Architect, Pivotal Application Transformation (AppTx) Allison Williams, Senior Solutions Architect, Pivotal AppTx
  2. 2. INTRODUCTIONS Allison Williams Program Lead, Federal Tom Collings Advisory Solutions Architect, Anchor
  3. 3. Methodology and Techniques • Portfolio level goals definition • Cloud suitability assessment and education • Define OKRs • Discuss timeline, staffing, risk, dependencies, etc. • One-week iterations • Hands-on code within 2-3 days • 1s to 10s of apps moved in 1s of weeks • Working code used to inform a cookbook of patterns Product Backlog (Pivotal Tracker) Boris Event Storming OKRs Slice Analysis Snap / SnapE Patterns ScopingDiscovery Ongoing Delivery Cycle We deliver working code via replatformed apps and modernized slices that prove out patterns Value Stream We work on a fixed timeline and spin this wheel many times, using the techniques as necessary Fixed Timeline Engagement Supported by a Paired Team
  4. 4. Our Service Offerings Re-Factor or Re-Build Prioritized, paired efforts focused on conversion of existing systems to cloud native application architectures. Often the work takes more time to complete but delivers significant business outcomes. Architecture Navigator A short, tactical service designed to solve problems (ex. A performance bottleneck within a cloud native application) and/or plan a solution (ex. Establish a path forward to modernize a complex “system of systems”). Re-Host or Re-Platform Targets mostly “self contained” applications deemed suitable for PCF or PKS. Focus on path-to-prod and maximizing the number of apps moved over and as far into prod as possible. Delivers IT outcomes. Program Delivery Mix of projects delivered over a longer time horizon by a mix of Pivotal and ecosystem partners. Scoped as a “journey” that gets started quickly and ramps responsibly based on feedback and measured outcomes. Typically dovetails into partner-led delivery at the right time as Pivotal shifts into an oversight and coaching role. Journey Navigator Baseline the path-to-production and lay initial groundwork for CI/CD automation. Define app migration funnel criteria and run using a set of apps from the portfolio. Deliver plan of tactical actions and strategic recommendations.
  5. 5. What AppTx Does - Journey Navigator TECH BIZ
  6. 6. What AppTx Does - Journey Navigator TECH BIZ
  7. 7. What AppTx Does - Journey Navigator TECH BIZ
  8. 8. What AppTx Does - Journey Navigator TECH BIZ
  9. 9. What AppTx Does - Journey Navigator TECH BIZ
  10. 10. System/Architecture Navigator
  11. 11. System/Architecture Navigator
  12. 12. System/Architecture Navigator
  13. 13. The 4 “Re’s” of Application Transformation Re-Host Containerize aka “lift and shift” Re-Platform Minimal efforts to run natively on PAS Re-Factor Convert to Cloud Native aka “Modernize” Re-Build Decompose and rewrite from the ground up Application Portfolio Funneling Process Business and Technical filters, prioritization, scheduling, etc.
  14. 14. Transformation
  15. 15. Transformation
  16. 16. Transformation
  17. 17. Transformation
  18. 18. Things that may seem like problems but really aren’t ● No experience with Cloud Native
  19. 19. Things that may seem like problems but really aren’t ● No experience with Cloud Native ● No experience with PCF
  20. 20. Things that may seem like problems but really aren’t ● No experience with Cloud Native ● No experience with PCF ● No experience with pairing
  21. 21. Things that may seem like problems but really aren’t ● No experience with Cloud Native ● No experience with PCF ● No experience with pairing ● Code not in great shape
  22. 22. Things that may seem like problems but really aren’t ● Pivotal doesn’t know the code
  23. 23. Things that may seem like problems but really aren’t ● Pivotal doesn’t know the code ● Pivotal doesn’t know the culture
  24. 24. Things that may seem like problems but really aren’t ● Pivotal doesn’t know the code ● Pivotal doesn’t know the culture ● Pivotal doesn’t know the business motivation
  25. 25. Common Problems: Ownership ● Devs don’t own their code/design
  26. 26. Common Problems: Ownership ● Devs don’t own their code/design ● Devs don’t own their automation
  27. 27. Common Problems: Ownership ● Devs don’t own their code/design ● Devs don’t own their automation ● Team does not have authority to make decisions
  28. 28. Common Problems: Commitment ● Lack of executive sponsorship
  29. 29. Common Problems: Commitment ● Lack of executive sponsorship ● No full-time PO
  30. 30. Common Problems: Commitment ● Lack of executive sponsorship ● No full-time PO ● Ticket completion times
  31. 31. Common Problems: Commitment ● Lack of executive sponsorship ● No full-time PO ● Ticket completion times ● No SMEs
  32. 32. Common Problems: Commitment ● Lack of executive sponsorship ● No full-time PO ● Ticket completion times ● No SMEs ● External distractions
  33. 33. Common Problems: Readiness ● Platform
  34. 34. Common Problems: Readiness ● Platform ● Facilities/Badges/Pairing
  35. 35. Common Problems: Readiness ● Platform ● Facilities/Badges/Pairing
  36. 36. Common Problems: Readiness ● Platform ● Facilities/Badges/Pairing ● Code Access
  37. 37. Common Problems: Readiness ● Platform ● Facilities/Badges/Pairing ● Code Access ● Backlog access
  38. 38. Common Problems: Culture ● Poor cross-org collaboration
  39. 39. Common Problems: Culture ● Poor cross-org collaboration ● Not used to XP
  40. 40. Common Problems: Culture ● Poor cross-org collaboration ● Not used to XP ● Failure leads to scapegoating
  41. 41. Common Problems: Culture ● Poor cross-org collaboration ● Not used to XP ● Failure leads to scapegoating ● Security is an after-thought
  42. 42. Summary Some Problems Aren’t Problems Many problems can be mitigated, but at the risk of slowing the team down due to spending time moving roadblocks instead of the code Do The Right Thing Do What Works Be Kind.
  43. 43. Q&A
  44. 44. Links: ● Webinar on AppTx offerings: https://content.pivotal.io/webinars/sep-5-application-migration-how-to-start-scale-and- succeed-webinar ● Slaying the Dragon: https://www.youtube.com/watch?v=neL3OQ1GRhY&t=16s

×