A Django database connector that enables using MongoDB as a backend without modifying the Django ORM.
Djongo is a database connector that allows Django projects to use MongoDB as a backend database while maintaining full compatibility with the Django ORM. It translates SQL queries into MongoDB query documents, enabling developers to leverage MongoDB's flexibility without altering their Django models or admin interface. This bridges the gap between Django's robust ORM and MongoDB's document-oriented flexibility.
Django developers who want to use MongoDB as their database backend without modifying their existing Django models, ORM queries, or admin interface.
Developers choose Djongo because it is the only connector that lets them use MongoDB with Django without changing the Django ORM, allowing them to retain all Django features like the admin GUI, contrib modules, and ORM compatibility while benefiting from MongoDB's document storage.
Django and MongoDB database connector
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Maintains all Django ORM features, including contrib modules like admin and auth, without code changes, as emphasized in the README's key features.
Enables direct management of MongoDB documents through the Django Admin interface, allowing CRUD operations as shown in the usage section.
Supports embedded models and arrays within Django models, leveraging MongoDB's document-oriented flexibility for nested data structures.
Easy installation via pip and minimal configuration in settings.py, with clear steps to get started quickly, as outlined in the usage instructions.
Translates SQL queries to MongoDB, which can introduce performance latency and may not optimize complex queries as efficiently as native MongoDB operations.
Relies on Django ORM abstraction, so advanced MongoDB features like aggregation pipelines might require workarounds or raw queries, limiting flexibility.
Requires MongoDB 3.4 or higher, and for nested queries, 3.6 or higher, which can be a barrier for environments with legacy database versions.