Asp.net MVC is it better to work with Areas or with Projects within a Solution? [closed]

Question

Asp.net MVC is it better to work with Areas or with Projects within a Solution? [closed]

Navigation

#1 by (2 votes)

1

I'm creating a portal and separating modules by Areas.

But the demands are increasing a lot, there are at least 5 more modules to be written on the portal.

What is the best way forward in terms of performace and organization? Continue in the MVC pattern by separating the modules by areas or separating them by projects within the Solution?

c# asp.net-mvc asp.net-mvc-5

asked by anonymous 17.05.2018 / 14:25

1 answer

Create and destroy session Statement of Pointers in a struct and calling it in function

score 2 · Accepted Answer

From a technical point of view, putting in other projects generates positives and negatives. Positive:

Placing on different projects will make your system more modular. As a benefit of this, you can stop a project while others continue to work . Ex: The shipping area can be stopped for maintenance while the concierge continues to operate. There is a name for this type of development approach: Microservice .

Negative points:

The complexity of your project will increase . You will have to manipulate login in both, configure two projects in IIS, manipulate DNS, consume more server resources etc.

In my opinion, from the organizational point of view does not change, you have separated them into folders internally.

On performance, we could only be sure of a better performance , if each project is put on a different server . If they are placed on the same server, only via stress tests and banchmarks we would know. Even so, likely not to make major differences by being on the same server .

It's up to you to analyze the technical strengths and weaknesses and decide what works best for you or your team. If the increase in scalability of the microservice compensates for the increase in the complexity of the system.