BLOGs - ASP.NET MVC, ADO.NET Data Services and ADO.NET Entity Framework - Component Architecture

Component Architecture - part two: technology stack

May14

Written by:Renato.Eccher
5/14/2009 3:09 AM

In part one (5/12/2009), I defined the responsibilities of the components of a data driven application. In this second part, I will show in what layer of the application architecture these components live. In addition, I define the technologies used to implement these responsibilities which I will address in detail in later blogs entries.

ASP.NET MVC View: a view transforms the model data into a representation that the client understands; in the above example into HTML.
Model Representation: this is a representation of the model data and is the result of executing the ASP.Net renderer after the MVC View was invoked.
Stylesheet: CSS stylesheets are responsible for creating the look&feel. It is executed and interpreted(!) by the browser.
Scripts: scripts like stylesheets are executed by the browser. Scripts in form of jQuery are used to enhance the user experience.
ASP.NET MVC Controller: the controller receives the user request and either invokes the Data Service layer to retrieve or to persist model(s).
ASP.NET MVC Model: models are objects created by the Entity Framework and represent copies of the data stored in the relational database.
ADO.NET Data Services: provides access to the model and hosts the business rule layer. Thes busines rules are implemented with Filters and Validators and are executed by the Data Service interceptors.
BR Filters: filters are applied whenever a controller requests models. Filters implement the business rules that restrict access to data. I.e. Query restrictions on who sees what from the business.
BR Validators: validators are invoked whenever a controllers inserts, updates or deletes any models. Validators implement business rules that enforce the business model constraints. I.e. Modifications rules on when and how data enters the business.
ADO.NET Entity Framework: Entity framework (EF) is responsible for persisting the model. This object relational mapper (ORM) takes care of persisting models into the relational database and vice versa. EF lets you design your domain or business model graphically in visual studio (VS2010), map the attributes and relations to the database schema and code generates the classes of the model.

Trackback Print

Location: Blogs

My Blogs

Tags:

0 comment(s) so far...

Your name:
Your email:
	(Optional) Email used only to show Gravatar.
Your website:
Title:
Comment:

Security Code Enter the code shown above in the box below
Add Comment Cancel