Documents
Resources
Learning Center
Upload
Plans & pricing Sign in
Sign Out

The Ado.NET Entity Framework Architecture

VIEWS: 130 PAGES: 2

The Ado.NET Entity framework belongs to the .NET framework family and its main purpose is to extract the logical schema of the data and offer it in the form of conceptual schema to the application. Transactions help Microsoft dot net development to integrate with transactional abilities of the underlying store while metadata services helps in managing metadata in regard to relationships, entities and mappings.

More Info
									The Ado.NET Entity Framework Architecture
The Ado.NET Entity framework belongs to the .NET framework family and its main
purpose is to extract the logical schema of the data and offer it in the form of conceptual
schema to the .net application development. It is a known fact that .net developers
have to study a large amount of code and easing this problem is the Ado.Net entity
framework. One of the main objectives is to help .Net application development capitalize
on the advantages of the high level of abstraction that is needed for data programming
thereby removing the mismatch that exists between languages and data models. The
.NET developers are prevented from the dilemma of dealing with the confusion that the
mismatch can create. The Entity Framework is available as part of the ADO.Net family
of Microsoft dot net development platform.

In order to understand the role that Ado.Net entity framework plays and the platform
that it offers to .Net development outsource companies, it is important to
understand its architecture. The architecture of Ado.Net Entity framework comprises of
                                        various components and they include:

                                        Specific Data Source Providers:

                                        The main function of this component is to
                                        abstract the Ado.Net interfaces thereby enabling
                                        Asp.Net developers to connect it with the
                                        database when programming takes place against
                                        the conceptual scheme.

                                        EDM Parser:

This particular component along with view mapping picks up the SDL specification
maps it onto the relational model and then facilitates programming against the
conceptual model. Therefore, this helps .Net application development by assimilating
information from multiple tables and then aggregating them into an independent entity.

Query and update:

There is a query and update pipeline that helps in processing queries, it then filters and
even updates requests to translate them into store specific queries through the help of
the map provider.

Transactions and Metadata Services:

Transactions help Microsoft dot net development to integrate with transactional
abilities of the underlying store while metadata services helps in managing metadata in
regard to relationships, entities and mappings.


http://www.aegisisc.com
                                                                                    Page 1
Conceptual Layer API:

This is the runtime that displays the programming model for coding and it helps .Net
developers to use the ADO.Net for utilizing connection objects while referring to the
map provider.

Disconnected Components:

In the complete process of .Net application development, this helps in locally caching
datasets and then utilizing Ado.Net entity framework in Entity Sets that contain the
results.

Design Tools:

.Net development outsource team also realizes that the Ado.Net framework also
includes design tools such as mapping designer, which helps in easing the process of
mapping a conceptual schema to the relational schema and also highlighting the
characteristics of an entity type.




http://www.aegisisc.com
                                                                                Page 2

								
To top