The most popular Entity Framework Core provider for MySQL and MariaDB, built on top of MySqlConnector for high-performance database communication.
Pomelo.EntityFrameworkCore.MySql is an Entity Framework Core provider that enables .NET applications to interact with MySQL and MariaDB databases using the standard EF Core API. It solves the problem of database persistence in .NET applications by providing a robust, high-performance bridge between Microsoft's ORM framework and popular open-source database systems. The provider supports all actively maintained MySQL and MariaDB versions and keeps pace with EF Core releases.
.NET developers building applications that require MySQL or MariaDB database persistence, particularly those using ASP.NET Core, Entity Framework Core, and modern .NET versions (6.0+).
Developers choose Pomelo.EntityFrameworkCore.MySql because it's the most popular and actively maintained EF Core provider for MySQL/MariaDB, offering reliable performance through MySqlConnector, comprehensive feature support, and timely updates that track both EF Core and database server releases.
Entity Framework Core provider for MySQL and MariaDB built on top of MySqlConnector
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Built on MySqlConnector for optimized database server interactions, ensuring better performance compared to alternatives, as highlighted in the key features.
Actively tested against all maintained MySQL and MariaDB versions, including LTS releases like MariaDB 10.11, providing broad support out of the box.
Implements the complete Entity Framework Core API surface, allowing seamless use of advanced EF Core features with MySQL/MariaDB, as stated in the description.
Offers additional packages for JSON support and spatial data with NetTopologySuite, enabling database-specific features without custom work.
Requires precise alignment of EF Core, .NET, and MySqlConnector versions, which can lead to configuration errors and upgrade challenges, as shown in the compatibility table.
Newer releases have phased out support for .NET Framework and older .NET Core versions, forcing teams on legacy systems to stick with outdated provider versions.
The README warns that debugging options like sensitive data logging should be changed or removed for production, indicating default settings aren't optimized and require manual tuning.