什麼是雲端遷移? |雲端遷移策略

雲端遷移是將資料庫、應用程式和IT流程轉移到雲端,或從一個雲端轉移到另一個雲端的過程。

學習目標

閱讀本文後,您將能夠:

  • 了解什麼是雲端遷移
  • 探索為什麼企業要遷移到雲端
  • 了解遷移到雲端的一些挑戰
  • 探索各種雲端遷移策略

相關內容


想要繼續瞭解嗎?

收到最熱門網際網路深入解析的每月回顧!

請參閱 Cloudflare 的隱私權政策,了解我們如何收集和處理您的個人資料。

複製文章連結

什麼是雲端遷移?

網際網路雲端遷移

雲端遷移是將數位業務營運轉移到雲端的過程。雲端遷移有點像實體遷移,只是這涉及將資料、應用程式和 IT 流程從某些資料中心遷移到其他資料中心,而不是打包和遷移實體產品。就像從較小的辦公室遷移到較大的辦公室一樣,雲端遷移需要大量的準備工作和前期工作,但是通常值得為之付出努力,從而節省成本並提高靈活性。

Most often, "cloud migration" describes the move from on-premise or legacy infrastructure to the cloud. However, the term can also apply to a migration from one cloud to another cloud.

什麼是傳統基礎結構?

在運算中,如果硬體或軟體已過時但仍在使用,則將其視為「舊版」。舊版產品和流程通常不如最新解決方案有效和安全。被迫執行舊系統的企業會有落後於競爭對手的風險。他們還面臨著更高的資料外洩的危險。

舊版軟體或硬體可能會變得不可靠、執行速度緩慢或可能不再受原始供應商的支援。例如,Windows XP 是舊版作業系統:於 2001 年發布,其功能已被更高版本的 Windows 超越,並且微軟不再透過發佈修補程式或更新來支援該作業系統。

基礎結構包括伺服器、網路設備、應用程式、資料庫以及任何其他關鍵業務軟體或硬體。傳統的基礎結構 (例如老化的伺服器或實體防火牆設備) 可能會減慢公司的業務流程。隨著原始供應商放棄對其產品的支援並停止發佈安全性修補程式,這也可能增加更多的安全性風險。

Legacy infrastructure is typically hosted on-premise, meaning it is physically located in buildings or on property where the organization operates. For instance, many businesses host an on-premise data center in the same building where their employees work.

Companies that rely on on-premise legacy infrastructure are unable to experience the benefits of cloud computing. Because of this, most enterprises today have made at least a partial migration to the cloud.

遷移到雲端的主要優勢是什麼?

  • Scalability: Cloud computing can scale up to support larger workloads and greater numbers of users far more easily than on-premise infrastructure, which requires companies to purchase and set up additional physical servers, networking equipment, or software licenses.
  • 成本:遷移到雲端的公司通常會大大減少他們在 IT 營運上的支出,因為雲端提供者會處理維護和升級,這讓公司可以將更多的資源用於最重要的業務需求上——來開發新產品或改進現有產品。
  • Performance: For some businesses, moving to the cloud can enable them to improve performance and the overall user experience for their customers. If their application or website is hosted in cloud data centers instead of in various on-premise servers, then data will not have to travel as far to reach the users, reducing latency.
  • Flexibility: Users, whether they are employees or customers, can access the cloud services and data they need from anywhere. This makes it easier for a business to expand into new territories, offer their services to international audiences, and let their employees work flexibly.

遷移到雲端的主要挑戰是什麼?

實體雲端遷移
  • 遷移大型資料庫:通常,為了在雲端中運作,資料庫將需要完全遷移到另一個平台。移動資料庫是很困難的過程,尤其是在涉及大量資料的情況下。一些雲端提供者實際上提供了實體資料傳輸方法,例如將資料載入到硬體設備上,然後將設備運送到雲端提供商,以用於海量資料庫,而這些資料庫可能需要很長時間才能透過網路進行傳輸。資料也可以透過網路傳輸。無論採用哪種方法,資料遷移通常都需要花費大量時間。
  • 資料完整性:傳輸資料後,下一步是確保資料完整且安全,並且在此過程中不會洩漏。
  • Continued operation: A business needs to ensure that its current systems remain operational and available throughout the migration. They will need to have some overlap between on-premise and cloud to ensure continuous service; for instance, it is necessary to make a copy of all data in the cloud before shutting down an existing database. Businesses typically need to move a little bit at a time instead of all at once.

How does an on-premise-to-cloud migration work?

每個業務都有不同的需求,因此對雲端遷移將遵循略有不同的流程。雲端提供者可以幫助企業建立其遷移流程。大多數雲端遷移將包括以下基本步驟:

  1. 建立目標:企業希望看到哪些效能提升?舊式基礎結構將在什麼日期棄用?建立可衡量的目標有助於企業確定遷移是否成功。
  2. Create a security strategy: Cloud cybersecurity requires a different approach compared to on-premise security. In the cloud, corporate assets are no longer behind a firewall, and the network perimeter essentially does not exist. Deploying a cloud firewall or a web application firewall may be necessary.
  3. 複製資料:選擇一個雲端提供者,然後複製現有資料庫。在整個遷移過程中應連續進行此操作,以使雲端資料庫保持最新狀態。
  4. 移動商業智慧:這可能涉及重構或重寫程式碼 (請參見下文)。這可以逐步完成,也可以一次全部完成。
  5. Switch production from on-premise to cloud: The cloud goes live. The migration is complete.

Some businesses turn off their on-premise infrastructure at the end of these steps, while others may keep legacy systems in place as backup or as part of a hybrid cloud deployment.

企業應採用哪種雲端遷移策略?

權威的資訊技術研究公司 Gartner 為組織遷移到雲端提供了 5 種選擇。這些雲端遷移策略通常稱為「5 R's」:

  • 重新託管——重新託管可以理解為「除了部署在雲端伺服器,其他皆不變」。選擇此策略的公司將選擇 IaaS (基礎結構即服務) 提供者,並在該基礎結構上重新建立其應用程式體系結構。
  • 重構——選擇重構的公司將重用已經存在的程式碼和框架,但在 PaaS (平台即服務) 提供者的平台上執行其應用程式,而不是像在重新託管中那樣在 IaaS 上執行。
  • 修訂——此策略涉及部分重寫或擴展程式碼庫,然後透過重新託管或重構來部署 (請參見上文)。
  • 重建——「重建」意味著在 PaaS 的提供者平台上從零開始重寫和重新架構應用程式。這可能是一個勞動密集型過程,但這也使開發人員能夠利用 PaaS 提供者的現代功能。
  • 替換——企業還可以選擇完全放棄其舊應用程式,並從第三方供應商切換到已建構的 SaaS (軟體即服務) 應用程式。

公司應選擇哪種雲端部署方式?

除了雲端遷移策略外,企業還需要確定遷移完成後雲端部署的外觀。

A hybrid cloud mixes two or more types of environments, combining public clouds, private clouds, or on-premise legacy data centers. For a hybrid cloud deployment to work well, integration must be tight across all deployed clouds and data centers – just as team members need especially tight communication if they are spread out across different offices.

A multi-cloud deployment combines two or more public clouds. (Public clouds are shared by more than one customer.) Multi-cloud can serve several purposes: redundancy/backup, cost savings, or leveraging features from different cloud providers, for instance.

僅從一個雲端供應商部署單一雲端對於企業而言不一定可行,但這是一種選擇。雲端提供者同時提供公共雲端和私有雲端–區別在於私有雲端不與任何其他業務共享。

Cloudflare 如何幫助實現雲端遷移?

Cloudflare offers a single control plane for the performance and security products necessary to make a move to the cloud successful – such as DNS, load balancing, the Cloudflare WAF, and others. These products are all integrated and can all be managed from a single dashboard (see a cloud migration case study). Cloudflare integrates easily with any type of cloud deployment – public cloud, private cloud, hybrid cloud, or multi-cloud.

了解有關雲端運算如何運作的更多資訊。