should set up the folder structure before creating the projects in visual studio. It just becomes very confusing if you are asking the viewers to change the namespace, project location after setting up the structure
The clean architecture is pretty clear in this video. thanks for this. However, it shows the layering of one web API (API, Core and infrastructure layers). If we consider micro-service architecture, i mean when multiple Web API projects can be there (similar to FeedbackService) in one solution, how the layering should be?? Will the other new-service also will go under 'src' folder with 3 different projects (new-service.Api, new-service.Core and new-service.Infrastructure)? I am not able visualize this. Can you please help me out? Or the general practice is to create multiple solutions for each microservice?
Thanks for the feedback. I'd recommend to have three projects for each Microservice because initially service might be small but when you keep adding more & more API endpoints then managing logic and repos everything in one project might be difficult but if you know that your service will not grow at the beginning of the desing then it’s okay to have one project but that is not clean architecture though; Yes, I’d recommend to have separate solution and git repo for each microservice; I am planning to discuss these in details as part of my another series on “Microservices architecture” You can check my icodeforu.com/ website for more details
I disagree with the structure of where the repository needs to sit. It is currently dependant on the infrastructure's entity. It should have been the other way around. Placing the context in the infrastructure and repository in infrastructure.
I wish I could give you a thousand likes, justice was done to the explanation
i reall like your video! great guide
can you share document for this project.
should set up the folder structure before creating the projects in visual studio. It just becomes very confusing if you are asking the viewers to change the namespace, project location after setting up the structure
The clean architecture is pretty clear in this video. thanks for this. However, it shows the layering of one web API (API, Core and infrastructure layers). If we consider micro-service architecture, i mean when multiple Web API projects can be there (similar to FeedbackService) in one solution, how the layering should be?? Will the other new-service also will go under 'src' folder with 3 different projects (new-service.Api, new-service.Core and new-service.Infrastructure)? I am not able visualize this. Can you please help me out?
Or the general practice is to create multiple solutions for each microservice?
Thanks for the feedback.
I'd recommend to have three projects for each Microservice because initially service might be small but when you keep adding more & more API endpoints then managing logic and repos everything in one project might be difficult but if you know that your service will not grow at the beginning of the desing then it’s okay to have one project but that is not clean architecture though;
Yes, I’d recommend to have separate solution and git repo for each microservice; I am planning to discuss these in details as part of my another series on “Microservices architecture”
You can check my icodeforu.com/ website for more details
@@anji.keesari thank you very much for your suggestion 👍
super cool. Thanks for this series.
Glad you enjoy it!
why are you using configureawait ?
I disagree with the structure of where the repository needs to sit. It is currently dependant on the infrastructure's entity. It should have been the other way around. Placing the context in the infrastructure and repository in infrastructure.