MongoDB Provider for Entity Framework Core Now Generally Available

Taylor Pacelli
May 3, 2024 | Updated: May 8, 2024
#MongoDB.local NYC '24

We are pleased to announce that the MongoDB Provider for Entity Framework Core (EF Core) is now generally available. This allows developers using EF Core to build C# and .NET applications with MongoDB and to take advantage of our powerful developer data platform while continuing to use APIs and design patterns they already know and love.

This post is also available in: Deutsch, Français, Español, Português, Italiano, 한국어, 简体中文.

Building for the C# and .NET communities

Nearly one-third of all developers use C# to build applications, with the population of C# developers reaching upwards of 10 million developers worldwide. What’s more, 39 percent of C# developers use EF Core, which is beloved as an abstraction layer to simplify working with data during development. In the past, C# developers could use MongoDB’s C# driver but didn’t have first-party support for EF Core, so some turned to community-built projects that could be helpful—but lacked official backing or ongoing support from MongoDB.

With the official MongoDB Provider for EF Core now generally available, developers can confidently use C# and EF Core when building with MongoDB for production-grade workloads.

Gaurav Seth, Partner Director, Product Management at Microsoft, shared his excitement about the new integration, highlighting its importance for the .NET developer community:

We are pleased to deepen the relationship between .NET developers and MongoDB through the new MongoDB Provider for Entity Framework Core,” said Gaurav Seth. “This advancement bridges the gap between MongoDB and Entity Framework Core, enabling .NET developers to leverage the full spectrum of MongoDB’s capabilities within the familiar EF environment. With this integration, .NET developers can now more easily incorporate MongoDB’s powerful features into their EF-based applications, further enhancing the robustness and scalability of their solutions.

Gaurav Seth, Partner Director, Product Management at Microsoft

What's in the new Provider for EF Core

With the general availability release, the MongoDB Provider for EF Core offers developers the following capabilities, building upon the foundational features released in the public preview:

  • Compatibility with Entity Framework Core 8 & .NET 8: Fully compatible with the latest EF Core and .NET versions, ensuring your projects are up-to-date with the newest features and improvements.

  • Advanced Querying and Data Operations: Provides a comprehensive suite of querying options, including complex operations and aggregates like Where, OrderBy, and ThenBy, enabling precise data retrieval and deeper analytical insights within your applications.

  • Mapping and Configuration Flexibility: Extended mapping capabilities for properties and entities, including support for various data types and composite keys, providing greater flexibility and precision in how data is structured and stored.

  • Array and List Handling: Improved handling of arrays and lists, enabling more complex data structures to be easily managed and manipulated within your applications.

  • Logging: Enhanced logging for better visibility of operations.

We will continue to offer support for the following capabilities launched in the Public Preview:

  • Support for code-first workflows: Allows users to build without an initial database; you create the classes for your application and then match your data model to the classes, not the other way around.

  • Basic CRUD methods: Basic create, read, update, and delete (CRUD) operations are supported.

  • String and numeric type operators: String and numeric type operators needed for basic CRUD operations will be supported. We anticipate supporting more complex operators in future iterations of the Provider.

  • Embedded documents: The Provider supports embedded documents, making it easier to store related information in the same database record.

  • Class mapping and serialization: Your classes in C# will map to MongoDB in a predictable way, including when working with IDs as well as date and/or time values.

  • LINQ query support: The Provider will support LINQ queries with fluent query syntax.

  • Change tracking: The Provider allows you to track and save changes made to entities with each DbContext instance back to your MongoDB database.

Benefits of using the Provider for EF Core

With the MongoDB Provider for EF Core, C# developers can unlock the full power of MongoDB's developer data platform to build modern applications while leveraging a familiar API interface, query paradigm (LINQ), and design patterns. Developers looking to modernize their data layer can do so with MongoDB while remaining free from cloud vendor lock-in since MongoDB works with all major cloud providers and for multi-cloud deployments.

How to get started with MongoDB Provider for Entity Framework Core

All you need to do is download the MongoDB Provider for EF Core from the NuGet package manager and build a DbContext that points to a MongoDB Provider instance. The Provider connects to MongoDB and handles the rest, so you can quickly harness the joint value of EF Core and MongoDB.

Learn more by diving into our documentation. After you try the new Provider for EF Core, leave us feedback. Your input is important for helping us continue to improve the product experience.

Get started today to unleash the power of your data with MongoDB and EF Core.

← Previous

适用于 Entity Framework Core 的 MongoDB 提供程序现已正式发布。

我们很高兴地宣布，适用于 Entity Framework Core (EF Core) 的 MongoDB 提供程序现已正式发布。这可以让使用 EF Core 的开发者借助 MongoDB 来构建 C# 和 .NET 应用程序，并充分利用我们强大的开发者数据平台，同时继续沿用他们已经熟悉和喜爱的 API 和设计模式。 面向 C# 和 .NET 社区构建 近 三分之一的开发者使用 C# 来构建应用程序，全球 C# 开发者人数已超过 1,000 万 。此外， 39% 的 C# 开发者使用 EF Core 。EF Core 作为在开发过程中简化数据处理工作的抽象层，深受广大开发者的欢迎。过去，C# 开发者可以使用 MongoDB 的 C# 驱动程序，但无法获得针对 EF Core 的第一方支持。因此，部分开发者转向可能有所助益的社区构建的项目，但又缺少来自 MongoDB 的官方支持或持续支持。 现在，随着适用于 EF Core 的官方 MongoDB 提供程序的正式发布，开发者在使用 MongoDB 构建生产级工作负载时可以放心地使用 C# 和 EF Core。 Microsoft 产品管理合作伙伴总监 Gaurav Seth 分享了自己对这项新集成的喜悦心情，并强调了它对于 .NET 开发者社区的重要性： 适用于 Entity Framework Core 的全新 MongoDB 提供程序可进一步增进 .NET 开发者和 MongoDB 之间的关系，我们对此感到非常高兴，”Gaurav Seth 表示。“该提供程序弥合了 MongoDB 和 Entity Framework Core 之间的差别，使 .NET 开发者能够在自己熟悉的 EF 环境中充分利用 MongoDB 的所有强大功能。通过这项集成，.NET 开发者现在可以更轻松地将 MongoDB 的强大功能整合到基于 EF 的应用程序中，以进一步增强解决方案的稳健性和可扩展性。 Gaurav Seth，Microsoft 产品管理合作伙伴总监 适用于 EF Core 的全新提供程序包含的功能 在正式发布版本中，适用于 EF Core 的 MongoDB 提供程序在公开预览版所发布的基础功能之上，为开发者提供了以下功能： 与 Entity Framework Core 8 和 .NET 8 兼容： 与 EF Core 和 .NET 的最新版本完全兼容，确保项目保持最新状态，能够获得最新的功能和改进。 高级查询和数据操作： 提供一整套查询选项，包括 Where、OrderBy 和 ThenBy 等复杂的操作和聚合，从而在应用程序内实现精确的数据检索和更深入的分析洞察。 灵活的映射和配置： 扩展了属性和实体的映射功能，包括对各种数据类型和复合键的支持，从而为数据的结构化和存储提供了更大的灵活性和精确度。 数组和列表处理： 改进了数组和列表的处理，使开发者能够在应用程序内轻松管理和操作更复杂的数据结构。 日志记录： 增强了日志记录功能，提高了操作的可见性。 我们会继续为公开预览版中推出的以下功能提供支持： 支持代码优先的工作流 ： 允许用户在没有初始数据库的情况下构建；您先创建应用程序的类，然后将数据模型与这些类匹配，而不是以相反的顺序进行。 基本 CRUD 方法： 支持基本的创建、读取、更新和删除 (CRUD) 操作。 字符串和数值类型的操作符： 支持基本 CRUD 操作所需的字符串和数值类型的操作符。我们计划在未来发布的提供程序版本中支持更复杂的操作符。 嵌入式文档： 该提供程序支持各种嵌入式文档，让您能够更轻松地将相关信息存储在同一个数据库记录中。 类映射和序列化： C# 中的类将以可预测的方式映射到 MongoDB，包括在使用 ID 以及日期和/或时间值时。 LINQ 查询支持： 该提供程序支持具有流畅的查询语法的 LINQ 查询。 更改跟踪： 该提供程序支持您跟踪使用每个 DbContext 实例对实体所做的更改，并将这些更改保存回 MongoDB 数据库。 使用适用于 EF Core 的提供程序的好处 借助适用于 EF Core 的 MongoDB 提供程序，C# 开发者可以充分利用 MongoDB 开发者数据平台的强大功能来构建现代应用程序，同时又能继续利用他们已经熟悉的 API 接口、查询范例 (LINQ) 和设计模式。希望现代化其数据层的开发者可以利用 MongoDB 实现这一目标，同时又不必受限于特定的云服务提供商，因为 MongoDB 适用于所有主流云服务提供商且支持多云部署。 如何开始使用适用于 Entity Framework Core 的 MongoDB 提供程序 您只需从 NuGet 软件包管理器下载适用于 EF Core 的 MongoDB 提供程序，并构建指向 MongoDB 提供程序实例的 DbContext。该提供程序会连接到 MongoDB 并执行后续步骤，方便您快速利用 EF Core 和 MongoDB 搭配使用带来的诸多优势。 深入阅读我们的 文档 ，了解更多信息。 体验了适用于 EF Core 的全新提供程序后，欢迎留下您的 反馈 。您的意见有助于我们持续改进产品体验。 立即开始使用 ，通过 MongoDB 和 EF Core 充分释放数据潜力。

May 3, 2024
Next →

Payments Modernization and the Role of the Operational Data Layer

To stay relevant and competitive, payment solution providers must enhance their payment processes to adapt to changing customer expectations, regulatory demands, and advancing technologies. The imperative for modernization is clear: payment systems must become faster, more secure, and seamlessly integrated across platforms. Driven by multiple factors—real-time payments, regulatory shifts like Payment Services Directive 2 (PSD2), heightened customer expectations, the power of open banking, and the disruptive force of fintech startups—the need for payment modernization has never been more pressing. But transformation is not without its challenges. Complex systems, industry reliance on outdated technology, high upgrade costs, and technical debt all pose formidable obstacles. This article will explore modernization approaches and how MongoDB helps smooth transformations. Approaches to modernization As businesses work to modernize their payment systems, they need to overcome the complexities inherent in updating legacy systems. Forward-thinking organizations embrace innovative strategies to streamline their operations, enhance scalability, and facilitate agile responses to evolving market demands. Two such approaches gaining prominence in the realm of payment system modernization are domain-driven design and microservices architecture : Domain-driven design: This approach focuses on a business's core operations to develop scalable and easier-to-manage systems. Domain-driven design ensures that technology serves strategic business goals by aligning system development with business needs. At its core, this approach seeks to break down complex business domains into manageable components, or "domains," each representing a distinct area of business functionality. Microservices architecture: Unlike traditional monolithic architectures, characterized by tightly coupled and interdependent components, a microservices architecture decomposes applications into a collection of loosely coupled services, each of which is responsible for a specific business function or capability. It introduces more flexibility and allows for quicker updates, facilitating agile responses to changing business requirements. Discover how Wells Fargo launched their next-generation card payments by building an operational data store with MongoDB . Modernizing with an operational data layer In the payments modernization process, the significance of an operational data layer (ODL) cannot be overstated. An ODL is an architectural pattern that centrally integrates and organizes siloed enterprise data, making it available to consuming applications. The simplest representation of this pattern looks something like the sample reference architecture below. Figure 1: Operational Data Layer structure An ODL is deployed in front of legacy systems to enable new business initiatives and to meet new requirements that the existing architecture can’t handle—without the difficulty and risk of fully replacing legacy systems. It can reduce the workload on source systems, improve availability, reduce end-user response times, combine data from multiple systems into a single repository, serve as a foundation for re-architecting a monolithic application into a suite of microservices, and more. The ODL becomes a system of innovation, allowing the business to take an iterative approach to digital transformation. Here's why an ODL is considered ideal for payment operations: Unified data management: Payment systems involve handling a vast amount of diverse data, including transaction details, customer information, and regulatory compliance data. An ODL provides a centralized repository for storing and managing this data, eliminating silos and ensuring data integrity. Real-time processing: An ODL enables real-time processing of transactions, allowing businesses to handle high numbers of transactions swiftly and efficiently. This capability is essential for meeting customer expectations for instant payments and facilitating seamless transactions across various channels. Scalability and flexibility: Payment systems must accommodate fluctuating transaction volumes and evolving business needs. An ODL offers scalability and flexibility, allowing businesses to scale their infrastructure as demand grows. Enhanced security: An ODL incorporates robust security features —such as encryption, access controls, and auditing capabilities—to safeguard data integrity and confidentiality. By centralizing security measures within the ODL, businesses can ensure compliance with regulatory requirements and mitigate security risks effectively. Support for payments data monetization: Payment systems generate a wealth of data that can provide valuable insights into customer behavior, transaction trends, and business performance. An ODL facilitates real-time analytics and reporting by providing a unified platform for collecting, storing, and analyzing this data. Transform with MongoDB MongoDB’s fundamental technology principles ensure companies can reap the advantages of microservices and domain-driven design—specifically, our flexible data model and built-in redundancy, automation, and scalability. Indeed, the document model is tailor-made for the intricacies of payment data, ensuring adaptability and scalability as market demands evolve. Here’s how MongoDB helps with domain-driven design and microservice implementation to adopt industry best practices: Ease of use: MongoDB’s document model makes it simple to model or remodel data to fit the needs of payment applications. Documents are a natural way of describing data. They present a single data structure, with related data embedded as sub-documents and arrays, making it simpler and faster for developers to model how data in the application will be mapped to data stored in the database. In addition, MongoDB guarantees the multi-record ACID transactional semantics that developers are familiar with, making it easier to reason about data. Flexibility: MongoDB’s dynamic schema is ideal for handling the requirements of microservices and a domain-driven design. Domain-driven design emphasizes modeling the domain to reflect the business requirements, which may evolve over time. MongoDB's flexible schema allows you to store domain objects as documents without rigid schema constraints, facilitating agile development and evolution of the domain model. Speed: Using MongoDB for an ODL means you can get better performance when accessing data, and write less code to do so. A document is a single place for the database to read and write data for an entity. This locality of data ensures the complete document can be accessed in a single database operation that avoids the need internally to pull data from many different tables and rows. Data access and microservice-based APIs: MongoDB integrates seamlessly with modern technologies and frameworks commonly used in microservices architectures. MongoDB's flexible data model and ability to handle various data types, including structured and unstructured data, is a great fit for orchestrating your open API ecosystem to make data flow between banks, third parties, and consumers possible. Scalability: Even if an ODL starts at a small scale, you need to be prepared for growth as new source systems are integrated, adding data volume, and new consuming systems are developed, increasing workload. MongoDB provides horizontal scale-out on low-cost, commodity hardware or cloud infrastructure using sharding to meet the needs of an ODL with large data sets and high throughput requirements. High availability: Microservices architectures require high availability to ensure that individual services remain accessible even in the event of failures. MongoDB provides built-in replication and failover capabilities, ensuring data availability and minimal downtime in case of server failures. Payment modernization is not merely a trend but a strategic imperative. By embracing modern payment solutions and leveraging the power of an ODL with MongoDB, organizations can unlock new growth opportunities, enhance operational efficiency, and deliver superior customer experiences. Learn how to build an operational data layer with MongoDB using this Payments Modernization Solution Accelerator . Learn more about how MongoDB is powering industries on our solution library .

May 15, 2024