An Entity Framework Core provider for MongoDB, enabling .NET developers to interact with MongoDB using familiar EF Core patterns.
MongoDB Entity Framework Core Provider is an open-source library that enables .NET developers to use Entity Framework Core to interact with MongoDB databases. It allows developers to write LINQ queries, use DbContext patterns, and perform CRUD operations on MongoDB while leveraging EF Core's familiar abstractions. It solves the problem of bridging MongoDB's document model with the object-relational mapping approach used in .NET applications.
.NET developers building applications with MongoDB who want to use Entity Framework Core for data access, particularly those migrating from relational databases or seeking consistency across data storage technologies.
Developers choose this provider because it offers the productivity and familiarity of EF Core with MongoDB's flexibility, reducing the learning curve for MongoDB in .NET ecosystems. Its support for transactions, vector search, and encryption compatibility provides advanced MongoDB features within the EF Core paradigm.
MongoDB Entity Framework Core Provider
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Provides full LINQ query support, DbContext patterns, and change tracking, allowing .NET developers to work with MongoDB using familiar abstractions from the README examples.
Integrates MongoDB-specific capabilities like vector search, client-side field-level encryption, and optimistic concurrency, as highlighted in the Supported Features section.
Offers auto-transactional SaveChanges for atomic commits, compatible with MongoDB 5.0+ transaction-enabled configurations, ensuring data integrity.
Enables mapping of sub-documents and embedded documents via owned entities, respecting MongoDB's document model while using EF Core conventions.
Lacks support for Includes/joins, GroupBy, and geospatial queries, which are essential for complex data relationships, as admitted in the Limitations section.
Does not include EF Core migrations, requiring manual handling of collection schemas and changes, which can increase maintenance overhead for evolving projects.
Version alignment with EF Core means breaking changes can occur in non-major releases, necessitating careful upgrades as documented in the Breaking Changes file.