Entity Framework tutorial -- EF architecture, entityef
EF Architecture
It is a panorama of the EF architecture, allowing us to understand the usefulness of each component separately.
EDM (Entity Data Model ):
EDM consists of three main parts: Conceptual Model, Mapping, and Storage Model ).
Conceptual Model:
Conceptual models include model classes and their relationships, which are not affected by database design.
Storage Model:
A storage model represents the design of a database, including tables, views, stored procedures, inter-Table relationships, and primary/Foreign keys.
Mapping:
Ing refers to converting a conceptual model into a storage model.
LINQ to Entities:
LINQ to Entities is the object query language used to compile the query object model. It can be used to return your defined conceptual model. Some techniques related to LINQ are used here.
Entity SQL:
Entity SQL is another query language similar to LINQ to Entities. However, it is a little more difficult than LINQ to Entities, and developers need to learn it separately.
Object Service:
Object service is the main portal to access the database and returns the accessed data. It is mainly responsible for some specific things, such as getting data from the entity client data provider (its next layer) and converting it into an object.
Entity Client Data Provider:
The primary responsibility of this layer is to convert the queries provided by LINQ to Entities or Entity SQL into queries that can be understood and executed by specific databases. It uses ADO. NET data provider to communicate with the database.
ADO. Net Data Provider:
This layer uses standard ADO. NET to communicate with databases.