How to decide which one should be used in an MVC web application or three-tier architecture?

If we need to choose one architecture pattern for a web application in .NET, which one will be the best, MVC or 3 levels, how to solve?

+3
source share
2 answers

Jeevan

I think that you, unfortunately, are following the idea that many developers new to MVC accept you to be “convinced” that “M” in mvc (model) is a pure implementation of linq2sql, and that this is for the model . Not so ... in our applications we have to serve a mixture of web / desktop and handheld devices using different areas of common functionality within them. therefore, we created the “BLL / DAL” DLL with all our business logic, which is referred to as “M” in our mvc applications. The same "bll / dal" is used in our webforms applications, as well as in our desktop applications. in one current application, we connect to the oracle server with our dll dll bll / dal and use MVC exclusively as a RESTful service, acting as an intermediary between two legacy systems.given the design of our dll bll / dal, we could just as easily switch this to sqlserver should (when and when) a business is required.

MVC 3 ( , , [ /]), , , .

, - mr google , .

[edit] - , SO; N- . , MVC N-.

MVC Vs n-level

, - /API, - ; .

+10

, . , . , , , (, + + ).

, 2, :

  • , .
  • , , .
  • ,

, , , 4 .

, ( ) MVC 3 , :)

+1

Source: https://habr.com/ru/post/1776621/


All Articles