谷歌中国开发者社区 (GDG)
  • 主页
  • 博客
    • Android
    • Design
    • GoogleCloud
    • GoogleMaps
    • GooglePlay
    • Web
  • 社区
    • 各地社区
    • 社区历史
    • GDG介绍
    • 社区通知
  • 视频
  • 资源
    • 资源汇总
    • 精选视频
    • 优酷频道

Choosing your cloud app migration order

2018-11-09adminGoogleCloudNo comments

Source: Choosing your cloud app migration order from Google Cloud

[Editor’s note: This post originally appeared on the Velostrata blog. Velostrata has since come into the Google Cloud fold, and we’re pleased to now bring you their seasoned perspective on successful cloud migrations. There’s more here on how Velostrata’s accelerated migration technology works.]

It’s a question we hear a lot: How do you decide the order in which you migrate applications into the public cloud? It’s a critical question, because early success during a cloud migration is crucial to continuing on your cloud adoption path. Inversely, early failure is an easy way to doom a project altogether. You might be on board with the benefits of public cloud, but wading through every application that’s been created or deployed in your business can be complicated and time-consuming. Although there’s no one-size-fits-all answer, there are some best practices you can use as you’re getting started evaluating your on-premises apps. This kind of up-front planning can make the migration process easier, and make the entire cloud transition smoother.

The following generic framework can help you best identify when workloads should be migrated.There are four ascending tiers that we see typically provide a good, logical migration order for workloads by group:

velostrata-pyramid.jpg

Tier 1: Opportunistic (especially to maximize ROI)

The first tier—strong candidates to migrate first—revolves around current opportunities that could help you maximize ROI of that app in some fashion. That’s especially useful if you’re under pressure to justify cloud business value or otherwise provide cost assessments for a workload or app. Here are some questions to ask to identify the applications to prioritize:

  • Is this application significantly more expensive to run on-prem than it would be to migrate and run in the public cloud?

  • Will this application require an upcoming hardware refresh, making it more attractive to move to the public cloud sooner rather than later?

  • Are there services (or regions/instances, etc.) in the cloud that would make this application perform significantly better?

Identifying these options to migrate can create some quick wins that yield tangible, immediate benefits for users and the business.

Tier 2: Minimize your migration risk

Where our first tier focuses on opportunity, our second tier focuses on risk. What applications can you move with relatively low risk to your greater IT operations? There are a number of questions IT can ask to help evaluate which applications are the least risky to migrate, making them the most attractive to migrate in the early phases of a cloud migration project. For example:

  • What is the business criticality of this application?

  • Do large swaths of employees and/or customers depend on this application?

  • What is the production level of this application (development vs. production)?

  • How many dependencies and/or integrations does this application have?

  • What is my IT team’s understanding of this application?

  • Does my IT team have proper, up-to-date, thorough documentation for this application and its architecture?

  • What are the operational requirements (SLAs) for this application?

  • What are the legal or governmental compliance requirements for this application?

  • What are the downtime and/or latency sensitivities for this application?

  • Are there line-of-business owners eager and willing to migrate their apps early?

Going through this list of questions can help you rank applications from lowest to highest risk. Low-risk applications should be migrated first, and higher-risk applications should come later.

Tier 3: Ease of migration to the public cloud

The third tier in this framework revolves around the ease with which you can potentially migrate an application to the cloud. Unlike risk, which is all about that application’s relative importance, ease of migration is about how frictionless the application’s journey to the cloud will be. Some good questions to ask include:

  • How new is this application, and was it designed to run on-prem or in the public cloud?

  • Can this application be migrated using straightforward approaches like lift-and-shift?

  • Is this application standardized for one OS type, or does it have flexible requirements?

  • Does this application (or its data) have regulatory, compliance, or SLA-based requirements to run on-prem?

When plotting out which applications to migrate to the cloud, you may find that sometimes applications from Tier 3 may go before Tier 2 (or even Tier 1). This is completely fine. Tier 2 and Tier 3 both involve a lot of variables, so it’s common to have some mixing and matching along your migration path.

Tier 4: Custom applications

The fourth and final tier of this framework—representing the applications you should migrate last—are your custom applications. These are applications that were written in-house or by third parties, but which will pose some potentially unique migration questions, like:

  • Was this application built specifically for its current hardware? For on-prem?

  • Do we have proper comments in the code to help us re-architect for the cloud if needed?

  • How is this application intertwined within our total application landscape?

  • Do we have the in-house expertise to migrate this application to the cloud successfully?

Answering these questions will help you have a sense of how (and whether) you’ll migrate these applications, and what challenges you might encounter along the way.

These four tiers represent a generic framework for you to decide the order in which to migrate your applications to the cloud. It’s crucial to get early wins during the migration process, and this framework can help you identify which applications represent the highest likelihood of early success. You can progress through your application landscape knowing which apps are most likely to yield success and which will be more challenging.

Learn more about cloud migration here, and happy planning!

除非特别声明,此文章内容采用知识共享署名 3.0许可,代码示例采用Apache 2.0许可。更多细节请查看我们的服务条款。

Tags: Cloud

Related Articles

Cloud TPUs in Kubernetes Engine powering Minigo are now available in beta

2018-09-15admin

Labelling and grouping your Google Cloud Platform resources

2018-06-13admin

Last month today: GCP in May

2018-06-05admin

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code class="" title="" data-url=""> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong> <pre class="" title="" data-url=""> <span class="" title="" data-url="">

Recent Posts

  • Five new investments for the Google Assistant Investments program
  • Expanding target API level requirements in 2019
  • The service mesh era: Securing your environment with Istio
  • Launchpad Accelerator Mexico now accepting startup applications
  • On the Path to Cryogenic Control of Quantum Processors

Recent Comments

  • Chen Zhixiang on Concurrent marking in V8
  • admin on 使用 Android Jetpack 加快应用开发速度
  • 怪盗kidou on 使用 Android Jetpack 加快应用开发速度
  • 鸿维 on Google 帐号登录 API 更新
  • admin on 推出 CVPR 2018 学习图像压缩挑战赛

Archives

  • February 2019
  • January 2019
  • December 2018
  • November 2018
  • October 2018
  • September 2018
  • August 2018
  • July 2018
  • June 2018
  • May 2018
  • April 2018
  • March 2018
  • February 2018
  • January 2018
  • December 2017
  • November 2017
  • October 2017
  • September 2017
  • August 2017
  • July 2017
  • June 2017
  • May 2017
  • April 2017
  • March 2017
  • February 2017
  • January 2017
  • December 2016
  • November 2016
  • October 2016
  • September 2016
  • August 2016
  • May 2016
  • April 2016
  • March 2016
  • February 2016
  • January 2016
  • December 2015
  • November 2015
  • October 2015
  • September 2015
  • August 2015
  • July 2015
  • June 2015
  • January 1970

Categories

  • Android
  • Design
  • Firebase
  • GoogleCloud
  • GoogleDevFeeds
  • GoogleMaps
  • GooglePlay
  • Google动态
  • iOS
  • Uncategorized
  • VR
  • Web
  • WebMaster
  • 社区
  • 通知

Meta

  • Log in
  • Entries RSS
  • Comments RSS
  • WordPress.org

最新文章

  • Five new investments for the Google Assistant Investments program
  • Expanding target API level requirements in 2019
  • The service mesh era: Securing your environment with Istio
  • Launchpad Accelerator Mexico now accepting startup applications
  • On the Path to Cryogenic Control of Quantum Processors
  • Re-thinking federated identity with the Continuous Access Evaluation Protocol
  • Real-time diagnostics from nanopore DNA sequencers on Google Cloud
  • Google Cloud Next ‘19 session guide now available
  • Making AI-powered speech more accessible—now with more options, lower prices, and new languages and voices
  • Cloud Services Platform—bringing hybrid cloud to you

最多查看

  • 谷歌招聘软件工程师 (21,041)
  • Google 推出的 31 套在线课程 (20,139)
  • 如何选择 compileSdkVersion, minSdkVersion 和 targetSdkVersion (18,761)
  • Seti UI 主题: 让你编辑器焕然一新 (12,693)
  • Android Studio 2.0 稳定版 (8,963)
  • Android N 最初预览版:开发者 API 和工具 (7,934)
  • 像 Sublime Text 一样使用 Chrome DevTools (5,950)
  • Google I/O 2016: Android 演讲视频汇总 (5,520)
  • 用 Google Cloud 打造你的私有免费 Git 仓库 (5,506)
  • 面向普通开发者的机器学习应用方案 (5,201)
  • 生还是死?Android 进程优先级详解 (4,971)
  • 面向 Web 开发者的 Sublime Text 插件 (4,140)
  • 适配 Android N 多窗口特性的 5 个要诀 (4,105)
  • 参加 Google I/O Extended,观看 I/O 直播,线下聚会! (3,477)
© 2018 中国谷歌开发者社区 - ChinaGDG