MRS
asked on
Using MVC or Web API for Restful APIs in .net CORE
Hey all,
I am working on redesigning our main CRM for a rewrite. We are primarily a .NET shop so I am thinking MVC for the front end, but I am trying to figure out the best design approach for the middle tier (business logic). I am pretty sure I want to expose the data layer via a restful API, so WebAPI on .NET CORE seems to be a good fit.
In my research, I had a couple question.
Thanks in advance.
I am working on redesigning our main CRM for a rewrite. We are primarily a .NET shop so I am thinking MVC for the front end, but I am trying to figure out the best design approach for the middle tier (business logic). I am pretty sure I want to expose the data layer via a restful API, so WebAPI on .NET CORE seems to be a good fit.
In my research, I had a couple question.
- As I delve more and more into MVC, it seems that could just as easily return an "object" from a controller as I could a view. If that is the case, is there any reason not to just include my API logic in the MVC application instead of making a separate project?
- I have learned that I can use scaffolding to generate classes automatically from the database, is there a way to automatically generate controllers for my classes?
- (I know this one is pretty general) Are there other/better technologies I should be looking at?
Thanks in advance.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER