> For the complete documentation index, see [llms.txt](https://dailyjournal.gitbook.io/notes/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dailyjournal.gitbook.io/notes/databases/non-relational-databases/mongodb.md). # MongoDB {% embed url="" %} * an open-source NoSQL database written in C++ language. * uses JSON like documents with optional schemas. * inbuilt support for data partitioning (Sharding) Features * Indexing * Aggregation * Special Collection and index types * File Storage * Sharding ### Scaling * The documented oriented data model of MongoDB makes it easier to split data across multiple servers. * Balancing and loading data across a cluster is done by MongoDB. It then redistributes automatically. ![](/files/fuHT0Nd6Z7WwiS8BkFYa) * The mongos acts as a query router, providing an interface between client applications and sharded cluster. * Config servers store metadata and configuration settings for the cluster. Each sharded cluster must have its own config servers. * MongoDB uses the config servers to manage distributed locks. Geospatial Indexes Types * 2dsphere * 2d --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://dailyjournal.gitbook.io/notes/databases/non-relational-databases/mongodb.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.