Bazel)<\/a>, an enormous effort impacting greater than 100 squads throughout the corporate.\u00a0\u00a0<\/p>\nKey challenges<\/h3>\n
We imagine that migrations will develop into more difficult as our codebase and group develop in measurement and complexity. We want to contemplate such difficult migrations to be the norm going ahead, if we wish to ship platform options effectively and at scale for cellular at Spotify.\u00a0<\/p>\n
Below are some challenges that we confronted throughout our journey. We\u2019ve supplied the eventualities with signs (\u201cWhen\u201d), what you need to keep away from when dealing with the state of affairs (\u201cDon\u2019t\u201d), and what we recommend that you simply do (\u201cDo\u201d).<\/p>\n
Challenge 1: Defining the scope<\/h4>\n
How can we create change and produce standardized architectural options that help most use circumstances with out undermining others?<\/p>\n
WHEN:\u00a0<\/strong><\/p>\n\n- The scope appears large \u2014 there\u2019s a sense that quite a few use circumstances should be addressed.<\/li>\n
- It\u2019s troublesome to know the place to start with the quantity of tech debt, modifications required, and use circumstances to help.<\/li>\n
- Stakeholders attain out a number of occasions, not totally understanding what they’re presupposed to do through the migration.<\/li>\n<\/ul>\n
DON\u2019T:<\/strong><\/p>\n\n- Try to establish all doable eventualities earlier than rolling out the answer.<\/li>\n
- Start a big migration with out an estimated roadmap and definition of success.<\/li>\n
- Reach out to stakeholders and not using a clear definition of what they should do.<\/li>\n<\/ul>\n
DO:<\/strong><\/p>\n\n- Know your objectives. Create a product transient that explains what you might be doing, why you might be doing it, and the way you’re going to do it.<\/li>\n
- Focus on the values. Changing them is time-consuming, however reframe objectives to higher align when wanted.<\/li>\n
- Address your viewers. Understand their psychological fashions so that you could speak about what\u2019s related, join the place their wants are, and discover proxies to broaden your attain.<\/li>\n
- Start small. Create a proof of idea, validate it with stakeholders, and get the migration by means of alpha, beta, and GA product lifecycles. Add use circumstances as you uncover them, mapping out the commonest ones first. This will mean you can get sufficient suggestions and incrementally help the completely different use circumstances.<\/li>\n
- Collaborate! Collaboration is vital within the early phases. Find early adopters who’re wanting to attempt your options and can develop into ambassadors in their very own tribes. This will finally assist with scalability as properly.\u00a0<\/li>\n<\/ul>\n
Challenge 2: Scaling up<\/h4>\n
How can we drive massive architectural and infrastructure modifications sooner in a hyper-growing group?\u00a0<\/p>\n
WHEN:\u00a0<\/strong><\/p>\n\n- Large numbers of squads are impacted by the modifications (greater than 100 squads).<\/li>\n
- There is a big quantity of labor \u2014 together with guide refactorings that should be performed by the squads through the migration.<\/li>\n
- Progress is sluggish \u2014 there\u2019s an enormous variety of stakeholders and dependencies.<\/li>\n
- Stakeholders are overwhelmed with the continuing migrations.<\/li>\n<\/ul>\n
DON\u2019T:<\/strong><\/p>\n\n- Believe that enormous infrastructure and structure modifications are inconceivable or not wanted in a big group.<\/li>\n
- Conform with shifting slower when making infrastructure\/architectural modifications.\u00a0<\/li>\n<\/ul>\n
DO:<\/strong><\/p>\n\n- Focus on stakeholder administration. Identify the completely different stakeholders so as of precedence. Be involved with them (e.g., Slack, e-mail teams). Tell them concerning the significance of your effort.\u00a0<\/li>\n
- Communicate. Keep your viewers engaged by sharing the progress by means of newsletters and office posts.\u00a0<\/li>\n
- Look to automation. Simplify the migration course of by investing in automation upfront. Do that you must refactor the code? Could the identical step be performed mechanically utilizing a script?\u00a0<\/li>\n
- Make time for spike weeks. Partner with squads and tribes to collectively dedicate every week to work on the migration.\u00a0<\/li>\n
- Use a number of assets to extend your attain. Education applications can assist onboard groups to new ideas and migrations, with the potential for making use of them immediately.\u00a0<\/li>\n
- Introduce the corporate\u2019s engineering practices within the onboarding applications to make sure that new joiners perceive and comply with the really useful finest practices from the beginning.<\/li>\n<\/ul>\n
Challenge 3: Competing priorities<\/h4>\n
What\u2019s the steadiness between having platform groups working to cut back tech debt and undertake new applied sciences versus holding squads accountable for the standard of the code they personal?<\/p>\n
WHEN:\u00a0<\/strong><\/p>\n\n- Stakeholders are concerned in high-priority initiatives and have little time to undertake your options.<\/li>\n
- Stakeholders suppose they’re slowed down by platform migrations and usually are not motivated to undertake new applied sciences.\u00a0<\/li>\n
- Projects dilute and the crew(s) driving the migration feels unmotivated, probably with some members leaving.<\/li>\n
- Code modifications are vital and in battle with the path of the migration.<\/li>\n<\/ul>\n
DON\u2019T:<\/strong><\/p>\n\n- Believe that stakeholders perceive the significance and influence of your migration and can prioritize it \u2014 they’ve loads of different work to do as properly.<\/li>\n
- Give in. \u201cWe are busy working on a higher-priority bet\u201d is a typical argument to not execute on platform migrations.<\/li>\n
- Consider the metrics and objectives to be set in stone and troublesome to vary.<\/li>\n<\/ul>\n
DO:<\/strong><\/p>\n\n- Motivate. Showcase the optimistic influence of your migration to stakeholders and encourage them to get the work performed.<\/li>\n
- Continuously consider. Have common checkpoints through the quarter to guage the velocity of the migration to succeed in your quarterly, half-yearly, or yearly objectives.\u00a0<\/li>\n
- Manage threat. If the migration is shifting slowly, how are you going to tweak the method to succeed in the objectives? Can you streamline the method? Do you want extra engineers? Can you rent contractors? Can you affect different tribes to deliver your efforts to their backlog?<\/li>\n
- Take the ache on-platform. When doable, make the required modifications on behalf of the group to allow them to concentrate on creating enterprise worth for our customers.<\/li>\n
- Monitor modifications that go towards migration KPIs and create channels with groups to help them.<\/li>\n<\/ul>\n
Challenge 4: Being accountable<\/strong><\/h4>\nHow will we maintain groups accountable and hold them engaged within the adoption of latest applied sciences that require massive infrastructure modifications and refactoring?<\/p>\n
WHEN:<\/strong><\/p>\n\n- There\u2019s an absence of accountability within the adoption of latest applied sciences, therefore migrations are taking longer.<\/li>\n
- It\u2019s exhausting to foretell when the migration will finish.<\/li>\n<\/ul>\n
DON\u2019T:<\/strong><\/p>\n\n- Expect there to be inside\/exterior alignment when driving massive modifications over time.<\/li>\n
- Think that it\u2019s exhausting to measure the progress and influence of infrastructure modifications.<\/li>\n<\/ul>\n
DO:<\/strong><\/p>\n\n- Delineate the definition of performed. Use information and pattern graphs to present projections. It\u2019s necessary to grasp the place you might be ranging from and how briskly you might be progressing so that you could estimate how briskly you’ll transfer sooner or later and whether or not that you must make any changes to hurry up the migration.<\/li>\n
- Present your progress. Take management of the definition of success and talk typically to maintain your viewers engaged and onboarded together with your modifications.\u00a0<\/li>\n
- Use dashboards. Metrics and dashboards will talk the progress and influence, in addition to assist prioritize your work at scale over time.\u00a0<\/li>\n
- Maintain a timeline. Keep your roadmap updated. Over time, your crew and stakeholders may change, they usually\u2019ll want to pay attention to your migration and timeline. A roadmap additionally will increase transparency, allows suggestions and collaboration, and helps establish any roadblocks.<\/li>\n<\/ul>\n
Conclusion<\/h3>\n
Migrations of this nature and magnitude may develop into a brand new regular \u2014 in any other case, it may be inconceivable for the corporate to carry out sure modifications. New applied sciences will come, and we are going to do the required migrations, although we must always reduce the disruption for groups. Some platform merchandise will inherently require migrations, and doubtlessly in a big scale, and we must always think about them a part of the event lifecycle, along with testing and design.\u00a0<\/p>\n
We\u2019ve discovered a terrific deal from this effort and hope that this information is beneficial for different groups driving massive migrations. If you wish to be taught extra about our challenges and the way we solved them, don’t hesitate to succeed in out to us.<\/p>\n
Special because of Marvin, Foundation, BoB, and Rubik for driving this effort.\u00a0\u00a0<\/p>\n
<\/p><\/div>\n
![\"\"\/](\"https:\/\/engineering.atspotify.com\/wp-content\/themes\/theme-spotify\/images\/icon.png\")
<\/p>\n![\"Strategies](\"https:\/\/storage.googleapis.com\/production-eng\/1\/2022\/11\/Strategies-and-Tools-for-Performing-Migrations-on-Platform.png\")
<\/a>