Migrating from MongoDB. Trying to understand how DocumentDB works.

i have mongodb database 21gb (and growing) , contains dozens of collections (clients, orders, etc.). toying idea of migrating documentdb.

first tried use documentdb's mongo api , failed miserably because documentdb doesn't support lot of mongodb features (aggregation, etc.). created 1 documentdb collection each mongodb collection, break bank me. 

on mongodb collection equivalent of table, common practice use 1 collection per entity hierarchy (one collection users, 1 collection products, etc). on documentdb, looks not same. can store several unrelated entities in single collection. correct?

also, getting different types of information depending on read documentdb. in 1 place read collection limit 250gb , don't have worry underlying complexity. on other places, read each partition 10gb , have assign partition keys collections. quite confusing used mongodb. if collection limit 250gb, need 1 collection store data. don't need have 1 throughput orders , different 1 clients. want them part of same database in traditional sense. 

so questions are:

1) can move 21gb of data multiple mongodb collections single documentdb collection?

2) if yes, have worry partitions @ all?

thanks in advance. 

hello,

depending on type of experience , interaction documentdb, have couple different solutions. if have time, can email me @ anhoh{at}microsoft{dot}com. i'd better understand use case provide clearer guidance.

- andy

Microsoft Azure  >  Azure Cosmos DB