Loading content
Entity Framework Core is a lightweight, extensible, open-source ORM for .NET. It enables developers to work with databases using .NET objects, supports LINQ queries, change tracking, and migrations. EF Core is suitable for relational databases and integrates with ASP.NET Core applications.
Use this profile to understand the building block briefly, place it in the model, and open related building blocks.
Technical building block: can be automated, integrated, or operated.
Concrete cog in the system that works inside larger relationships.
Entity Framework Core is a lightweight, extensible ORM for .NET. It connects application code to relational databases through object models and reduces the usual data-access burden.
Microsoft introduced Entity Framework Core in 2016 as a new ORM line with similar but not complete parity to Entity Framework 6. The move responded to the limits of classic EF and to the shift to .NET Core: data access needed to become cross-platform, lighter weight, and openly developed without giving up object-model programming.
EF Core works with a `DbContext` as the session between application and database. Inside it, entity classes, queries, and change tracking form one shared model. LINQ describes what data is needed; the provider translates that into the database's SQL dialect. On save, the change tracker compares current state with original state, and migrations turn model changes into schema changes.
EF Core runs on the .NET platform and uses its runtime, language, and library ecosystem.
The context bundles the connection, queries, configuration, and work session with the database.
Classes and properties represent domain data and relationships in the object model.
Queries are written in C# and translated by the provider into database operations.
EF Core keeps track of which objects changed so it can coordinate saving and synchronization.
Model changes are turned into traceable steps that update the database schema.
EF Core is a good fit for relational business applications where .NET code, domain model, and database access should stay closely aligned, such as ASP.NET Core or service applications. The team still needs solid SQL and schema knowledge; providers do not always behave identically, and performance tuning, bulk operations, and migrations should be validated with representative tests.
Where this building block is located in the topic model.
No structure path available.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.