- Hands-On Cloud Solutions with Azure
- Greg Leonardo
- 232字
- 2021-06-10 19:44:38
Rehost
Rehosting is the basic approach to the lift and shift model. There are no code changes and it is basically the fastest way to migrate. I just want to remind everyone that this can be the costliest approach to moving to Azure, but is arguably the simplest.
We use this approach in the following situations:
- There is a need to move applications into Azure quickly
- Applications require being run on a VM
- You do not want to change code or can’t (no source code)
Once migrated, I will look for opportunities to optimize, but usually in this scenario there aren't many opportunities other than rapid scaling.. Let’s look at what this would look like:
Some good tools to assist in this type of migration are the following:
- Azure Site Recovery: https://azure.microsoft.com/en-us/services/site-recovery/
- Data Migration Tool: https://azure.microsoft.com/en-us/services/database-migration/
Now, it is at this point that we need to remember that this type of environment will need boundaries like an on-premise environment does, so don’t forget about your firewalls, load balancer, and routing. Quite a few organizations forget about these and then get burned on their budget because of the cost of these resources. With the complexity of on-premise networks, you should list all the resources you will need. Also, keep in mind, that you can use your licenses to help lower the cost of the VM in Azure.
- 控制與決策系統仿真
- 工業機器人工程應用虛擬仿真教程:MotoSim EG-VRC
- 城市道路交通主動控制技術
- PostgreSQL Administration Essentials
- AWS Certified SysOps Administrator:Associate Guide
- Arduino &樂高創意機器人制作教程
- Ceph:Designing and Implementing Scalable Storage Systems
- 機器人制作入門(第4版)
- 伺服與運動控制系統設計
- Wireshark Revealed:Essential Skills for IT Professionals
- 傳感技術基礎與技能實訓
- Appcelerator Titanium Smartphone App Development Cookbook(Second Edition)
- 歐姆龍CP1系列PLC原理與應用
- 單片機C語言編程實踐
- Ripple Quick Start Guide