Shulou(Shulou.com)06/01 Report--

Today, I would like to talk to you about what the ORM for .NET Core is like. Many people may not know much about it. In order to make you understand better, the editor summarized the following. I hope you can get something from this article.

While EF Core is striving to provide basic database features such as views and stored procedures, developers are also looking for ORM tools that meet their data access needs. Some relatively widely used ORM are listed below.

LLBLGen Pro Runtime Framework

LLBLGen Pro Runtime Framework is an "optional" ORM that is used in conjunction with the LLBLGen solid modeling tool. It is called "optional" here because it also works with other ORM such as Entity Framework.

Similar to Entity Framework,LLBLGen Pro Runtime Framework, it is also a complete OOP-style ORM (Full ORM). But it differs in several aspects, first of all, it focuses more on performance. Although the performance of EF Core is significantly higher than that of classical Entity Framework, they are still significantly lower than other ORM. Frans Bouma, author of LLBLGen Pro, launched a performance competition to compare the speed of various .NET data access and ORM implementations.

LLBLGen Pro Runtime Framework is also different from EF/EF Core in that it is not Context-bound. Each entity can track its own changes and manipulate the object graph in memory without maintaining an open context. This feature will undoubtedly be popular with DBA because there is no need to maintain an open context, which means that you do not need to maintain an open database connection, otherwise you need to manipulate the database connection pool.

Like most ORM for .NET Core, there are some restrictions on the Core version of LLBLGen Pro Runtime Framework. But these limitations are mainly limited to the. NET Core's own missing features. For example, TransactionScope is not currently supported by SqlClient, a small number of objects are binary serializable, and so on.

Dapper

The other is the well-known micro-ORM (Micro-ORM) product Dapper. Dapper is often considered the fastest ORM, almost always at the top of the .NET ORM benchmark.

Dapper is usually used to implement calls to the original SQL and materialize the query results, so it works pretty much the same on .NET and .NET Core. Unlike complete ORM, Dapper does not provide any SQL generation capabilities. Although many developers do not trust the SQL generated by ORM, this still makes Dapper more cumbersome to use than other ORM products.

LINQ to DB

LINQ to DB calls itself "one step away from micro-orm products such as Dapper, Massive, PetaPoco, etc." It does not have some features that can cause performance problems when used in Entity Framework, such as change tracking.

The Join operation in LINQ to DB is somewhat different. In EF, any "Join" operation that needs to be performed is actually treated as a sub-object or Collection. The generated SQL naturally uses the Join operation, but when the result set is materialized to an object, the execution of the SQL statement is no longer dependent on the Join operation.

LINQ to DB actually performs Join operations, which are implemented as "Left Join" and "Inner Join" operations. If you use EF to interpret LINQ, the generated statement, though slightly peculiar in syntax, better matches the actual operation of the database.

DevExpress XPO

EXpressPersistent Objects (XPO) is a commercial product. The Reddit user "- GrapH-" commented on it as follows:

I have been using DevExpress XPO for 11 years. In October, it began to support .NET Standard 2.0. Although it is a commercial product, the first .NET beta (v17.2.2) that supports the .NET Core will be available free of charge to all users. Further updates, although paid for, include visual design tools and technical support. Although this ORM is different from EF and has been around for a longer time (if I remember correctly, its first version was for .NET 1.1), it basically contains all the features required for applications of all sizes. Its demos and tutorials are available on https://github.com/DevExpress/XpoNetCoreDemos.

After reading the above, do you have any further understanding of ORM for .NET Core? If you want to know more knowledge or related content, please follow the industry information channel, thank you for your support.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.