NotAllAboutCode

Document DB s are known to be very good at searching data among billions or trillions of records , with little or no performance degradation. At the same time, they have one big limitation: they do not play well with too many relationships between entities. Databases are an essential part of most IT systems, as they are the containers of the most valuable “piece of the puzzle”: the Data .  Relational Databases ( RDBMS ) have been playing a major role in the Data Architecture , being a sort of standard in the software industry; products such as Oracle , Microsoft Sql Server , MySql have been used for almost any software or services worldwide for several years. Those are by now considered mature technologies, tested and refined over the years to cope with constantly challenging data requirements and new software paradigms coming up all the time. However, since a few years, Social Media Networks systems such as Facebook , Twitter , LinkedIn (to name a few), introduce

The company I work for is going under an incredible growth, opening stores worldwide on a monthly basis, as well as increasing its IT workforce and infrastructure accordingly, to cope with such growth. One important project recently implemented in the Enterprise Architecture of the company has been the Geographically Distributed Replica Set with MongoDB and Azure ( ReadDB as the “simple” name) Before this project, the main database used for this purpose was a Sql Server located in a data center in Amsterdam; for obvious reasons, stores in US and even more in Asia, experienced latency during the retrieval of data, which resulted in a non-optimal user experience. Since the main need for such stores is to present data to the customer (orders, customer details, etc), a ReadOnly database seemed to be the best solution. Based on the popularity that NoSql databases gained recently, after some research we opted to use MongoDB as the ReadDB , and its Replica Set featu