Should mvc web applications be level 3?

Question

In the near future I will develop a couple of web applications. They will probably be executed in asp.net mvc.

In my existing web applications running in delphi, the data access level is split into a completely separate application, sometimes running on a different server. This is done more for code reuse than for architectural reasons. This will not be a factor in the next application, as it will be new.

Does the redundant application have an application for accessing data in the mvc application? I will already separate business classes through the use of MVC, and I will use ORM to perform db-persistence.

Edit: Just to clarify; I use the term tier to refer to individual physical applications, more than just a logical partition or layer.

Answer 1

The term " Tier " in my experience usually refers to physical applications, for example. Client level and server level.

MVC - refers to the 3 " Layers " with the concern associated with the separation around the 3 problems that it describes in the model (data), view (UI), controller (App Logic).

Now that I have made this distinction regarding my terminology ..

mvc?

, (- , ), , . ORM, , , , ORM? (DAL) .

, , , , DAL ​​ , MVC.

, , , .

Answer 2

, , , (pysical) (/).

- - s # arp (code.google.com/p/sharp-architecture/) , ( ).

, : ayende.com/Blog/

- , , , , , . , teirs, ( , ).

Answer 3

Great comment Tobias.

I say, add enough layers so that it makes sense to you and simplifies its support. Also to pay attention to issues.