Lift and shift SSIS to the cloud by using Azure Data Factory

Build with an Azure free account. Get USD200 credit for 30 days and 12 months of free services.
Start free todayLearn how easy it is to migrate your existing MongoDB applications to Cosmos DB by using the MongoDB API. You will find out about the tools used in the process, see the code that leverages Cosmos DB, and learn about techniques for working around the differences between the two products.
Product info: azure.microsoft.com/en-us/services/cosmos-db/
Learn more: docs.microsoft.com/en-us/azure/cosmos-db/
Documentation: docs.microsoft.com/en-us/azure/cosmos-db/mongodb-migrate
Create a Free Account (Azure): https://aka.ms/azft-cosmos
I'll admit , the migration from a MongoDB application to Cosmos DB, from a developer / technical standpoint is simple. Where I struggle to convince clients to make this move is the cost. In CosmosDB, each collection requires its own , minimum 400 RTU, and some clients have complained when they transfer multiple collections, only their first collection is set to 400RTU , all others are set to 1000RTU, and they have no way through the Azure portal to set each collection to 400RTU.
Even if they did, the costs, compared to MongoDB's DBaaS offering, Altas, is a fraction of the cost, considering they don't charge per collection.
Until Microsoft offers a cost effective means to transfer MongoDB solutions to CosmosDB, this will prevent many MongoDB applications from changing their application data provider.
cool