Within the shell environment, developers can seamlessly integrate API calls into their select statements. This functionality not only facilitates experimentation with various operations but also allows for a more iterative approach before these calls are incorporated into broader codebases. The shell serves as a versatile platform where users can construct collections, add items, and engage in CRUD (Create, Read, Update, Delete) operations. Additionally, it supports filtering and querying capabilities, along with the ability to build indexes across multiple fields within a collection.
For those seeking comprehensive guidance, the GitHub wiki stands as the primary resource for DocumentDB documentation. While the current content may feel somewhat sparse and could benefit from additional examples, it is designed for developers looking for an alternative to MongoDB. Notably, DocumentDB offers an open-source license, distinguishing it from other options that may have more restrictive terms. As there is no software development kit (SDK) available at this time, developers will need to create their own API calls, which are based on MongoDB principles, making the transition for existing applications relatively straightforward.
Why this? Why now?
The impetus behind the DocumentDB initiative appears to be a bold vision to establish a standardized NoSQL API and engine, akin to the frameworks developed for SQL. Microsoft brings a wealth of experience from its involvement in standards organizations, particularly in crafting and implementing the critical tests necessary to ensure that any resulting standard adheres to established requirements. This endeavor reflects a commitment to enhancing the NoSQL landscape, providing developers with robust tools and frameworks to build upon.
