@andrewholloway-breward213
Hi Milan, thanks for this insight into the basic project setup which has been born out of experience. Just embarking on a new project and I am adopting DDD, CQRS and MediatR as having worked on a legacy project for the past 10 years I can see the benefits of this approach and I look forward to future videos!
@marna_li
Thanks for the video! It is important for beginners to know that once you get a hold of separating stuff you can adapt this structure to your case. Merge and rearrange. Even create your own modules and so. In my case I moved more towards a VSA and put controllers together with application code. As long as you clearly keep stuff logically separate it is OK.
@joseantonioteransuarez6840
To fully understand, could you do a CRUD for a single entity? So the communication between layers could be seen better 🙏
@DenisioRodrigues
This video is the best video when to talk in start configure you application with clean architecture.
@abdifatahAnnaati
Clean architectur subjective, so it's different for a lot of people.
Personally Mine is as Fellows(Folder structures)
Sol-Folder
Entities
Services
DTO(AddReq/EditReq/Res for each Entity plus some custom ViewModels)
Interfaces
Helpers
actual Services.....
Main Project
areas(if req)
@manofqwerty
Great video, I am trying to convince work to convert one of our solutions to implement the CLEAN architecture and this video has helped me focus my thoughts.
@jamesevans6438
Hey Milan, Great video and congrats on the MVP, you have been smashing it and are awesome!
@sagotgala
I'm really glad I found this channel. I was struggling to find these kind of videos before especially about DDD.
@justtomi-qp8qj
Thanks for sharing! There are some details that I would like to understand there... - As why do you have separate WebApi and Presentation layer? - Why is Application layer separate from Domain layer? Keep making great stuff!
@vitek0585
This is great for someone who is just starting interested in clean architecture 👍
@cansozbir
Oh man :) Yesterday I've created a CQRS + Clean architecture web API. I went back and forth on your videos to structure the project :) I wish I had waited one more day :)
@davidlester6673
Well done you have created a traditional n-tier layered application. The only thing that is different from 20/30 years ago is the name of the architecture.
@gianlucalocri
Very nice as always!!! But I didn't get the point on presentation project. What is supposed to go in there?
@alpsavasdev
I think splitting the infrastructure layer to multiple projects for each infrastructural concern (database, email gateway, other external apis) looks more maintainable. I did that in a few projects and helped me better organize and understand my codebase (inspiring from the "screaming architecture")
@caseyspaulding
Thanks. Best explanation I have found. Simple to the point
@user-rp9iis1en6h
Great one. Could you please extend this video and show us one step further such as how we can add a helloworld endpoint that will fetch data from db and return json response. Basically we wanted to learn where to plant view models, where to put services, where to put repository and make it workable.
@artemvolsh387
Love video, and channel as well. Find it very useful and educative. Thanks a lot!
@ToPFeE1234
Good explanation! Can't wait to see another architecture 😊
@bismarckmartinez1545
Nice video my dear Milan Jovanovic! ;D Congrats!
@MilanJovanovicTech