Entity Framework Tutorial--ef Architecture

EF Architecture

is a panorama of the EF architecture, giving us a separate look at the usefulness of each component.

EDM (Entity Data Model):

The EDM consists of 3 main parts, the concept module (conceptual model), the mapping (Mapping), and the storage module (Storage model).

Conceptual Model:

The conceptual model contains model classes and their relationships, which are not affected by the database design.

Storage Model:

The storage model represents the design of the database, including tables, views, stored procedures, inter-table relationships, and primary foreign keys.

Mapping:

Mapping refers to some of the information that transforms a conceptual model into a storage model.

LINQ to Entities:

LINQ to Entities is the query language for the entity that is used to write the query object model. It can be used to return the conceptual model that you define. There are some LINQ-related techniques used here.

Entity SQL:

Entity SQL is another query language like LINQ to Entities, however, it is a little bit more difficult than LINQ to entities, and developers need to learn differently.

Object Service:

The Object service accesses the primary portal of the database and returns the data that is accessed. It is primarily responsible for specific things, such as getting data from the entity client data provider (its next layer) and converting it to a solid object.

Entity Client Data Provider:

The primary responsibility of this layer is to translate queries provided by LINQ to Entities or entity SQL into specific databases to understand the queries that are executed. It uses the ADO data provider to communicate with the database.

ADO Data Provider:

This layer uses the standard ADO to communicate with the database.

Entity Framework Tutorial--ef Architecture