Azure local development set up - cache, queue, documentdb

113 Views Asked by At

There are two azure emulators supporting local development, "azure storage emulator" supporting queue, cache, blob etc while "azure documentdb emulator" supporting documentdb.

Before, we have everything in one mssql database, take snapshot of the database and use that as our local development database. But when we split the data into blob and documentdb, we don't see how we can create replicates / snapshot of blob and documentdb and use that in local dev. Is there a way to synchronize the data between azure documentdb with the database used in emulators?

2

There are 2 best solutions below

1
Fei Han On

we don't see how we can create replicates / snapshot of blob and documentdb and use that in local dev.

It seems that you’d like to use the copies of Blob and DocumentDB for development and testing. As far as I know, we could not directly import/copy data from Azure Blob to Azure storage emulator, I recommend that you could copy data from one container to another container for your local development and testing. Besides, you could import data/documents from a production DocumentDB to the emulator using DocumentDB data migration tool, to achieve it, you need to change the connection mode to Gateway (in the data migration tool with the target set to the local emulator, click Target Information > Advanced Options > Connection Mode > Gateway).

0
marc chen On

I think using the "Data Factory" porting data from one datasource to another datasource is the solution here? I just tried to port 2M rows from documentdb to an azure SQL database which is Premium, took 30, 40 mins to copy over 2M, that is good enough for our project.