Explanation
Migrate from on-premises or cloud implementations of MongoDB to Azure Cosmos DB with minimal downtime by using Azure Database Migration Service. Perform resilient migrations of MongoDB data at scale and with high reliability.
Scenario: Data migration from on-premises to Azure must minimize costs and downtime.
The application uses MongoDB JSON document storage database for all container and transport information.
References:
https://azure.microsoft.com/en-us/updates/mongodb-to-azure-cosmos-db-online-and-offline-migrations-are-now-
Topic 1, Wide World ImportersCase Study
Background
Wide World Importers is moving all their datacenters- to Azure. The company has developed several applications and services to support supply chain operations and would like to leverage serverless computing where possible.
Windows Server 2016 virtual machine
This virtual machine (VM) runs BizTalk Server 2016. The VM runs the following workflows:
* Ocean Transport - This workflow gathers and validates container information including container contents and arrival notices at various shipping pons.
* Inland Transport - This workflow gathers and validates trucking information including fuel usage, number of stops, and routes.
The VM supports the following REST API calls:
* Container API - This API provides container information including weight, contents, and other attributes.
* Location API - This API provides location information regarding shipping ports of call and trucking stops.
* Shipping REST API - This API provides shipping information for use and display on the shippi ng website- Shipping Data The application uses MogoDB JSON storage database for all container and transport information Shipping Website The site displays containers tracking information and containers content. The site is located at
http//.wideworldimporters.com/
Proposed solution
The on-premises shipping application must be moved to Azure. The VM has been migrated to a new Standard_Dl6s_v3 Azure VM by using Azure Site Recovery and must remain running in Azure to complete the BizTalk component migrations. You create a Standard_D16s_v3 Azure VM to host BizTalk Server. The Azure architecture diagram for the proposed solution is shown below:

Shipping logic app
The Shipping Logic app must meet the following requirements:
* Support the ocean transport and inland Transport workflows by using a Logic App.
* Support industry-standard protocol X12 message format for various messages including vessel content details and arrival notices
* Secure resources to the corporate VNet and use dedicated storage resources with a fixed costing model.
* Maintain on-premises connectivity to support legacy applications and final BizTalk migrations Shipping Function app Implement secure function endpoints by using app-level security and include Azure Active Directory (Azure AD) REST APIs The REST API's that support the solution must meet the following requirements:
* Secure resources to the corporate VNet.
* Allow deployment to a testing location within Azure while not Incurring additional costs,
* Automatically scale to double capacity during peak shipping times while not causing application downtime,
* Minimize costs when selecting an Azure payment model,
Shipping data
Data migration from on premises to azure must minimize costs and downtime Windows server 2016 VM The VM shows high network latency, jitter, and high CPU utilization. The VM is critical and has not been backed up in the past. The VM must enable a quick restore from a 7-day snapshot to include m-place restore ol disks in case of failure.
Shipping website and REST APIs
The following error message displays while you are testing the website.