Microservice Solution Structure in .NET Applications

I am developing an application using the microservice approach, and it is difficult for me to determine how these microservices will look in the visual studio project.

My initial approach is to create one visual studio solution for each microservice. Each solution will have the following projects:

  • Host
  • Business API
  • Data access level
  • Model
  • Interfaces (for DI)
  • Data access
  • Business API Tests

Thus, there are 7 projects for microservice. Somehow it seems that many projects are redefined for each solution.

Is this approach right? Has anyone built microservices with .net? What does your project configuration look like?

+4
source share
1

, .

, ? , Host, Logic ( , , DAL .., ) Tests.

. , . , - . . , ( - ...).

+3

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


All Articles