Does anyone else prefer an N-tier architecture after * sending * an MVC application?

  • Other SO tags have asked people if they prefer N-Tier or MVC architecture.
  • I'm not looking to continue discussing this topic.
  • I am looking for something more specific.

My question is:

Does anyone else prefer an N-tier architecture after submitting an MVC application?

The reason for my question is:

  • Before I submitted the MVC web application, I was not sure that it excels N-Tier Architecture.
    • In particular, if better unit testing was the only obvious advantage of MVC, I saw no reason to shift gears and adopt a new architecture.
  • But after submitting the MVC application, I see many advantages (which are listed in other threads).
+3
source share
1 answer

I can say that I used both options and prefer N-Tier. I still think its cleaner after all. I am using Layergen http://www.icemanind.com/LayerGen.aspx , which will automatically build data layers and business layers for me.

+1
source

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


All Articles