Writing catalogs into Azure DocumentDB

One of the features of a catalog is accessing the product list and details the company sells. There is a big difference between read and write operations, favoring the first one as the most frequent. At the web stage, write operations happen only when the catalog is updated, and publishing involves just a minimal time (seconds to minutes) compared to using them (days to weeks). So, if indexing operations take a while to succeed, it is not bad. Eventual consistency is not an issue.

Product information is not flat. It is complex and structured, as information such as categorization, technical properties, and localization are not scalar properties, but complex structure themselves. Many products share the same categories or information. Again as mentioned earlier, write operations happen as catalog publishing, not product insertion. So, there are no normalization issues, as the product is already managed into the relational database-based ERP. On the other...