What's the best project structure to maintain multiple modules and services ?
Hello,
i plan to develop modular project (similiar to CMS) and i am not sure what's the best option how to maintain project.
I would like to have everything under one solution. So what's an example ?
User/Service/Module:
- handling user registration, login and so on
- contains model, migrations...
WebModule MVC:
- contains forms, controller logic, calls to UserModule
MyService
- calls 3th party REST API
- contains model, migrations...
- can be used from other MVC module
I would like to cut dependencies between projects. There will be around 10-15 feature modules. Desired result is when i put UserModule to other project, different MVC i will just run migrations and it will be possible to use it. And here are some questions.
Develop custom modules and service modules as WebAPI projects or use projects references ?
Should i put all database models under one distinct project which will contain all migrations ?
What about projects deploying ?
Any other tips how to maintain ?
Net.Core
Thanks much, i appreciate every comment.
0 comments:
Post a Comment