Migrating Your Apps to the Cloud: How to do it and What to Avoid
1 like927 views
This document discusses strategies for migrating applications to the cloud. It outlines several service offerings from Pivotal Application Transformation (AppTx) focused on re-hosting, re-platforming, re-factoring, or re-building applications. Common problems encountered include lack of ownership, commitment, readiness, and cultures unsuited for extreme programming. However, many issues like inexperience can be mitigated. The document emphasizes doing the right thing, what works, and being kind.
Migrating Your Apps to the Cloud: How to do it and What to Avoid
- 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. INTRODUCTIONS Allison Williams Program Lead, Federal Tom Collings Advisory Solutions Architect, Anchor
- 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. 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. What AppTx Does - Journey Navigator TECH BIZ
- 6. What AppTx Does - Journey Navigator TECH BIZ
- 7. What AppTx Does - Journey Navigator TECH BIZ
- 8. What AppTx Does - Journey Navigator TECH BIZ
- 9. What AppTx Does - Journey Navigator TECH BIZ
- 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. Transformation
- 15. Transformation
- 16. Transformation
- 17. Transformation
- 18. Things that may seem like problems but really aren’t ● No experience with Cloud Native
- 19. Things that may seem like problems but really aren’t ● No experience with Cloud Native ● No experience with PCF
- 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. 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. Things that may seem like problems but really aren’t ● Pivotal doesn’t know the code
- 23. Things that may seem like problems but really aren’t ● Pivotal doesn’t know the code ● Pivotal doesn’t know the culture
- 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. Common Problems: Ownership ● Devs don’t own their code/design
- 26. Common Problems: Ownership ● Devs don’t own their code/design ● Devs don’t own their automation
- 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. Common Problems: Commitment ● Lack of executive sponsorship
- 29. Common Problems: Commitment ● Lack of executive sponsorship ● No full-time PO
- 30. Common Problems: Commitment ● Lack of executive sponsorship ● No full-time PO ● Ticket completion times
- 31. Common Problems: Commitment ● Lack of executive sponsorship ● No full-time PO ● Ticket completion times ● No SMEs
- 32. Common Problems: Commitment ● Lack of executive sponsorship ● No full-time PO ● Ticket completion times ● No SMEs ● External distractions
- 33. Common Problems: Readiness ● Platform
- 34. Common Problems: Readiness ● Platform ● Facilities/Badges/Pairing
- 35. Common Problems: Readiness ● Platform ● Facilities/Badges/Pairing
- 36. Common Problems: Readiness ● Platform ● Facilities/Badges/Pairing ● Code Access
- 37. Common Problems: Readiness ● Platform ● Facilities/Badges/Pairing ● Code Access ● Backlog access
- 38. Common Problems: Culture ● Poor cross-org collaboration
- 39. Common Problems: Culture ● Poor cross-org collaboration ● Not used to XP
- 40. Common Problems: Culture ● Poor cross-org collaboration ● Not used to XP ● Failure leads to scapegoating
- 41. Common Problems: Culture ● Poor cross-org collaboration ● Not used to XP ● Failure leads to scapegoating ● Security is an after-thought
- 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. Q&A
- 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