Get the source code for this video for FREE → the-dotnet-weekly.ck.page/ca-from-scratch Want to master Clean Architecture? Go here: bit.ly/3PupkOJ Want to unlock Modular Monoliths? Go here: bit.ly/3SXlzSt
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.
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!
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!
In theory, domain can be shared by many applications [because It depends on nothing] But, if that's not the case, create a Core project and put both your entities and your use cases in it. :)
1. It's a personal preference of mine. Separating the executable (WebApi) from the endpoints/controllers 2. You want to isolate the core domain, so that it's not polluted by external concerns
@@MilanJovanovicTech hmm isn't application layer as well your core domain (logic). By doing that you're somehow breaking YAGNI with the assumption that your domain will have different applications. Thanks for clarification!
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)
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.
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")
Two things I didn't understand so far: 1. What's the purpose of having a "Presentation" project additionally to the "WebApi" project? So far, I was used to have only the WebApi project. What would you put into the Presentation project? 2. Why did you add Serilog.AspNetCore to the WebApi project and not to the Infrastructure Project? Isn't logging an infrastructure-related topic?
1. Move the API endpoints/controllers into that project, along with any view models. More of a personal preference than a real necessity. 2. Ah, good point! I find it easier to leave Serilog registration there because of the tight ASP.NET Core coupling (registering on the HostBuilder). Of course, we can move all of the registration into AddInfrastructure. Now that I think of it, it makes perfect sense. Thanks for calling me out on that 😁
I would imagine the decision to use a clean architecture or other alternative is a decision for the development team. Surely the solution architecture shouldn't be so prescriptive as to dictate implementation detail like how to organise source code?
Solution architecture is one level above this, so it would be just a component. C1/C2 diagram perhaps, check it out. For something lower level than that, you can do C3/C4.
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 :)
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.
Nice video, thanks. Still eagerly awaiting your video on setting up a modular monolith with module registration. Perhaps you could use this video as a starting point by showing how to register two CA projects?
I think yes, this video will be a starting point, to a more complete series about CA. And then I plan to evolve it into Modular Monolith. But honestly, Modular Monolith is such a complex topic that it would probably be better off creating a detailed course about it (4-5 hours) and just explaining absolutely everything.
@@MilanJovanovicTech yeah make sense. Actually couple of year ago i heard on internet that is only good for development environment it would suck on production real world apps So i wasn’t sure about it, although i like it very much as it keeps code highly clean, readable and maintainable!
As I understand Prestentation project is a bridge to Application -> Domain and can consist of ViewModels/Models for WeApi/Razor Pages projects? At the same time there is a separate path from Api to Infrastructure -> Persistence which do not interfere with Application/Domain projects.
I'd be interested to see why you seperated WebApi and Presentation. I don't see the point at first glance >) But thanks for your service in this community! Love this channel so much.
The purpose of dependency injection is not to give you default settings which you then can use (the DependencyInjection class you created in backend/application layer) but that you inject the dependencies and settings on your own. This means that from the REST API project, you should be configuring the whole backend, no?
Thanks for the video. In some tutorials, there is no Presentation layer. And the REST Controllers, for example, are in the Application layer instead of Presentation layer. Do you have any thoughts on that, is this also valid ?
Both approaches are valid, imo. Depends on how much control you want to have over the Controllers and what they can access. One example where it makes sense to separate the endpoints is when building a Modular monolith.
No, You just mentioned that we have two options on how to structure the presentation layer, but didn't mention the benefits of separating the presentation into two projects. 😔
@MilanJovanovicTech Thanks for giving us this wonderful video. Also I have a question, when I go to register the "AddPresentation()" or "AddInfrastructure()" or "AddApplication()" inside the program.cs file, it gives me an error : 'IServiceCollection' does not contain a definition for 'AddPresentation' and no accessible extension method 'AddPresentation' accepting a first argument of type 'IServiceCollection' could be found (are you missing a using directive or an assembly reference?)'. Also, I have references all three projects inside the WebAPI project.
Thanks for the video. Can I create a web application that use that api directly or should i use web application controllers to call this api by client clases for example? If i can use it direcctly i am not sure if domain should contain logic like ViewModels, resources, etc. Very difficult to find Api with ddd and web application integration, everybody only talk about the api and i am so confused.
Hi Milan, thanks for the video! I have just one question though, why didn't you reference application project in infrastructure project? (PS: I am new with clean architecture concepts)
Great video, I guess for the unit tests, it will be in another project right? in this case, a unit test project? what references from the other projects should have this unit test?
Great Video simple and Clean :) Good idea will be to record comparison of clean architecture approaches of ardalis vs jason taylor template. One more idea maybe to record one without use of CQRS and MediatR in the Application layer. keep up the good work pozdrav iz Makedonije :)
When would you want to use this design over modular monolith? In the end both seems to be more favored to bigger monoliths rather than small microservices.
@@MilanJovanovicTech Would be a lot of projects in that single solution :) lets say you are using clean architecture and need to introduce some background processing like azure functions, for this its common you need to share code and entities. Would that function app reference the same app/infra project or how would you go about this?
Have you or anyone implemented clean architecture in older versions of the .NET framework? The company I work for is still programming using this framework and it looks to me that we could also benefit from clean architecture also so I'd like to explore this possibility. It will be a plus of course if this has already been done to see how to approach this. Thanks
I can't remember the last time I used .NET Framework 😅 The biggest hurdle will be having a proper DI container to use. Everything else should be the same.
Thank you for this educational video that you sent. Do you have an example of a website or a small project that can be implemented and that I can understand the concept of this method and standard for me to check, or have you made a training video on this matter so far? Thank you.
@@MilanJovanovicTech I need to implement CQRS in another language. So i like to know which CA layer emits(i guess application layer) and which CA layers listen to the command and query. pls pardon my ignorance on CA on this aspect as I am trying on the same
I would disagree on a few points.. 1. The WebAPI project is your presentation layer, you do not need a separate "Presentation" project. 2: Logging wasn't relevant to the video but it should be abstracted to an ILogger and it's implementation should be moved to the infrastructure project. Obviously, these are just my opinions. Your videos are some of the best on RUclips for these topics.
1. Agreed, but this was about controlling direction of dependencies (if one needs it) 2. You can still use ILogger with Serilog | Obviously, these are just my opinions As are mine 😅 Most software engineering is opinionated.
Hi Milan! Thank you for the video. You pasted in the configuration for Serilog but there is a long line that is not visible towards the end. Can you share the whole code elsewhere please?
Where are the optionsetups added to the iservicecollection? All in application so that infrastructure and persistence can make use of them in their dependency injection class?
Thanks! Btw for anyone who was wondering about thjs. For EF it provided a provider to get the service options when declaring the options config (Milan shows that in a vid). But I found if that wasn't available I'd declare the options config with the setup class then use the buildservicdprovided method then with that get the options class I just binded to.
Hey Milan I like your work.. thanks for sharing your valuable experience with us.. i have a simple question for you could you please explain a bit why you put separate class lib presentation project either you can add your controller on you webApi project that you added at the end...its confusing what to do with presentation layer then.. thanks your answer will be appreciated
I was very confused when I heard that the presentation layer could be a REST Web API. In this case, which layer does my frontend built-in React that consumes this Web API belong to?
Hey Milan, first of all I like very much your videos :). Lately I also feel that the infrastructure indeed should be split in more parts like you did in your presentation: Intrastructure and Presentation and I have a question regarding this or at least I need confirmation for my thoughts :). For the case when I have an Api and a Cli built on top of my whole application then my infrastructure layer would be split in 3: Infrastructure (with core infra stuff), Presentation.Api, Presentation.CLI or? Thank you
I'd say the Infrastructure is irrelevant here. And the real question is Presentation - should we split it in two? If the entry points are different, and it looks like they are, then it makes sense
Thank you for your useful tutorial. I have a question regarding the Presentation layer what is the difference between it and the WebApi project? and in case I have a project consisting of several presentations such as gRPC, WebApi, MVC, etc., what is the good way to handle all of them in a single project?
WebApi is the composition root, and it brings them all together at runtime. Presentation is there to define the endpoints (entry points). You can move the Presentation into WebApi.
@@MilanJovanovicTech thank you for your so fast answer! and while i was waiting that i get one more question where i can store logger service? in infrastracture or application layer? or i can create another project and store that here
finally i land on the noob section please guide me into clean architecture. The Clean architecture and DDD series need to start from this vid😆 btw my VS not auto adding the using statemet :/ how do you do that ?
Thanks but ideally, as expected in Clean Architecture of Uncle Bob : the Application Layer should be TECHNOLOGY AGNOSTIC, so in this layer : no dependency injection Tool, no Mediatr, and so on. All of this should go into the Infra Layer !
Thank you for your video. Best explanation I've found. I have a question. Is it correct to the WebAPI layer know about Infrastructure Layer? Some diagrams in the internet show that Application and Domain Layers only work with Infrastructure layer
Within this example video, does the Presentation Layer Reference the Application Layer (MediatR Nuget was added into the Application project). ? Nice vid.
hey milan!! I saw your serilog video and implement serilog in my project. its great.. but i need logs to print in seperate folders for each controller. can you please help me out or make another video about serilog with indepth configurations. thanks 👍
@@MilanJovanovicTech thanks for your reply, really appreciate it. I'm trying to wrap my head around this properly. Would use cases/ business logic that span several aggregates interfaces and implementation both sit in application layer? Should those go in the same folder? I'd like see some good examples of this. Adding to this question would an entities IRepository be in a shared entity folder in the domain layer and then implementation be in the persistence layer? Then my use case services interface and implementation would use those repositories and sit in the application layer?
Shouldn't logging be configured inside the infrastructure layer ? I've seen CA aproaches using Serilog this way. Is it more optimal to configure it inside the API layer on .NET latest versions?
Hi @MilanJovanovicTech, I know this is an old video, but I'm learning about minimal APIs in .Net 8 and clean architecture. I have all my clean architecture structure inside the web API project and I want to separate it into the layers in this tutorial (a project for each layer of the clean architecture). I was able to separate the structure into projects and I'm trying to add the EndpointRouteBuilderExtensions class into the infrastructure layer, but i cannot implement the IEndpointRouteBuilder interface inside the infrastructure project, as this project is a class library project instead of a webapi project. Is there a way to add a reference inside the Infrastructure project in order to get the IEndpointBuilder interface and use it?
What if some of the domain models are linked to the IdentityUser like navigation property, while IdentityUser is a part of "Microsoft.AspNetCore.Identity.EntityFrameworkCore", what is the workaround for that? does it violate the Clean Architecture by just adding that?
@@MilanJovanovicTech yes this is the approach I took; kept it as a separate module and context. All working well, there are cases where Application needs to know the identity users id. Would be interested to see how you would approach this.
You mentioned that the API doesnt need to import the domain layer, because it will implicitly get it from the application layer, what do you mean by that, when the application layer doesnt hold the domain logic. Was this something you did not meant to say, or could you elaborate on what you mean. Right now my API needed to import also the domain layer, since thats where the models, exceptions etc are stored. But if you have a way to get to the domain from application, I am all open minded.
When writing for example a microservice or another type of project when all the business logic can only be exposed by webapi calls: I like handling all the validation as a middleware for webapi controllers or minimal APIs. That way your services/CQRS handlers and even domain classes do not need to be populated with validation and checks like the length of the email, etc
![SahBabii - Viking [Official Music Video]](http://i.ytimg.com/vi/D37cL92JX0I/mqdefault.jpg)
Get the source code for this video for FREE → the-dotnet-weekly.ck.page/ca-from-scratch
Want to master Clean Architecture? Go here: bit.ly/3PupkOJ
Want to unlock Modular Monoliths? Go here: bit.ly/3SXlzSt
@milan, is this included in your clean architecture course? I got your course but do I need to study this separately ?
Do you have any example plz ?
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.
Being pragmatic about architecture is something that comes with experience :)
@@MilanJovanovicTech Yes. 🙂
@@MilanJovanovicTech i would also like to see that
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!
Thanks a lot Andrew. I have a bunch of older videos also talking about these topics.
To fully understand, could you do a CRUD for a single entity? So the communication between layers could be seen better 🙏
Started something like that, watch the next video
@@MilanJovanovicTech I am waiting for this.
ruclips.net/video/nE2MjN54few/видео.html
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!
In theory, domain can be shared by many applications [because It depends on nothing]
But, if that's not the case, create a Core project and put both your entities and your use cases in it. :)
1. It's a personal preference of mine. Separating the executable (WebApi) from the endpoints/controllers
2. You want to isolate the core domain, so that it's not polluted by external concerns
@@MilanJovanovicTech hmm isn't application layer as well your core domain (logic). By doing that you're somehow breaking YAGNI with the assumption that your domain will have different applications.
Thanks for clarification!
@@MilanJovanovicTech So what code actually ends up in your Api project? Just the startup class?
@@pilotboba Pretty much yeah, just an entry point. Maybe some middleware? But those can also live elsewhere.
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)
Agreed, find what works for you
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.
Glad it was helpful!
Very nice as always!!! But I didn't get the point on presentation project. What is supposed to go in there?
Separating the executable from the endpoints. So controllers, minimal Apis, view models.
This video is the best video when to talk in start configure you application with clean architecture.
Thanks!
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")
You can make it as granular as you want, or not granular at all
@@MilanJovanovicTech IMHO “horizontal” granularity is not a problem at all, compared to vertical layering which causes a lot of indirection.
Two things I didn't understand so far:
1. What's the purpose of having a "Presentation" project additionally to the "WebApi" project? So far, I was used to have only the WebApi project. What would you put into the Presentation project?
2. Why did you add Serilog.AspNetCore to the WebApi project and not to the Infrastructure Project? Isn't logging an infrastructure-related topic?
1. Move the API endpoints/controllers into that project, along with any view models. More of a personal preference than a real necessity.
2. Ah, good point! I find it easier to leave Serilog registration there because of the tight ASP.NET Core coupling (registering on the HostBuilder).
Of course, we can move all of the registration into AddInfrastructure. Now that I think of it, it makes perfect sense. Thanks for calling me out on that 😁
@@MilanJovanovicTech could you provide an example of that approach? Sounds interesting.
@@MilanJovanovicTech Can you show how you would move the Serilog registration into the AddInfrastructure?
As a solutions architect, how do you document your architecture design so devs can understand and follow it?
I would imagine the decision to use a clean architecture or other alternative is a decision for the development team. Surely the solution architecture shouldn't be so prescriptive as to dictate implementation detail like how to organise source code?
Solution architecture is one level above this, so it would be just a component. C1/C2 diagram perhaps, check it out.
For something lower level than that, you can do C3/C4.
I usually document using the arc42 template in a markdown format alongside with my code. This way it's always versioned, too.
I'm really glad I found this channel. I was struggling to find these kind of videos before especially about DDD.
More DDD videos next week 😁
@@MilanJovanovicTech That's great!
Hey Milan, Great video and congrats on the MVP, you have been smashing it and are awesome!
Hey, thanks!! 😊
This is great for someone who is just starting interested in clean architecture
👍
I'll try to make some more beginner friendly content :)
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 :)
Ah, you never know 🤣
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.
Take a look at the few videos after that
Thanks for sharing! Ace Milan Jovanović
Glad you liked this one 😁
Nice video, thanks. Still eagerly awaiting your video on setting up a modular monolith with module registration. Perhaps you could use this video as a starting point by showing how to register two CA projects?
I think yes, this video will be a starting point, to a more complete series about CA. And then I plan to evolve it into Modular Monolith.
But honestly, Modular Monolith is such a complex topic that it would probably be better off creating a detailed course about it (4-5 hours) and just explaining absolutely everything.
Good explanation! Can't wait to see another architecture 😊
VSA coming
@@MilanJovanovicTechGood choice!
thank you explaining things with diagrams. very clean
You are welcome!
Have you ever used MediatR in production? How was you experience with MediatR in terms of performance and memory consumption in case of high traffic?
Yes, worked well for me. But I can't KNOW it will work well for you. Run some load testing perhaps with your expected traffic?
@@MilanJovanovicTech yeah make sense. Actually couple of year ago i heard on internet that is only good for development environment it would suck on production real world apps
So i wasn’t sure about it,
although i like it very much as it keeps code highly clean, readable and maintainable!
I like this better than the vertical approach.
Why so?
Thanks. Best explanation I have found. Simple to the point
I think you'll enjoy my Clean Architecture course, it's coming out soon
+1 for blank solution
I might be onto something
Nice video my dear Milan Jovanovic! ;D Congrats!
Thank you very much!
Love video, and channel as well. Find it very useful and educative. Thanks a lot!
Thank you for watching! 😊
As I understand Prestentation project is a bridge to Application -> Domain and can consist of ViewModels/Models for WeApi/Razor Pages projects? At the same time there is a separate path from Api to Infrastructure -> Persistence which do not interfere with Application/Domain projects.
Yes, you get it 😁
Thanks for sharing.
I would love to see how you fill out all the layers in a demo app.
I'll try to make it happen, layer by layer
Someone has been reading Eric Evans and Robert C. Martin! :D Great video Milan!
I've been influenced by them a lot, for better or worse
I'd be interested to see why you seperated WebApi and Presentation. I don't see the point at first glance >)
But thanks for your service in this community! Love this channel so much.
Separating the executable from the endpoints. So controllers, minimal Apis, view models in their own project.
Comes down to preference. Nothing major.
@@MilanJovanovicTech So you create do WebApi only for controllers?
The presentation class library will contains the filters and mappers for example?
The purpose of dependency injection is not to give you default settings which you then can use (the DependencyInjection class you created in backend/application layer) but that you inject the dependencies and settings on your own. This means that from the REST API project, you should be configuring the whole backend, no?
You can use either approach
Thanks for the video. In some tutorials, there is no Presentation layer. And the REST Controllers, for example, are in the Application layer instead of Presentation layer. Do you have any thoughts on that, is this also valid ?
Both approaches are valid, imo. Depends on how much control you want to have over the Controllers and what they can access. One example where it makes sense to separate the endpoints is when building a Modular monolith.
You (may) forgot to make the cursor visible. Great video. I'm subscribing.
Thanks! I'm working on Pragmatic Clean Architecture course right, which you might also enjoy :)
@@MilanJovanovicTech good news. I’ll be looking forward to it!
enjoying the content, subscribed already
Happy to have you :)
Great video Milan, my only concern is why you separate the presentation layer into two projects, what's the benefit you obtain by doing that?
Didn't I explain that in the video? 🤔
No, You just mentioned that we have two options on how to structure the presentation layer, but didn't mention the benefits of separating the presentation into two projects. 😔
@MilanJovanovicTech Thanks for giving us this wonderful video. Also I have a question, when I go to register the "AddPresentation()" or "AddInfrastructure()" or "AddApplication()" inside the program.cs file, it gives me an error : 'IServiceCollection' does not contain a definition for 'AddPresentation' and no accessible extension method 'AddPresentation' accepting a first argument of type 'IServiceCollection' could be found (are you missing a using directive or an assembly reference?)'. Also, I have references all three projects inside the WebAPI project.
Missing a using statement then?
Love these kind of video's. Thank you for the effort!
Awesome, glad you liked it!
Hello, good video. At which layer would you place a payment API interface and implementation?
Application/Infrastructure
Hi ,Milan, Have you done any crude operations on this architecture ?
Video coming out today 1PM with CRUD API basics!
Thanks for the video. Can I create a web application that use that api directly or should i use web application controllers to call this api by client clases for example? If i can use it direcctly i am not sure if domain should contain logic like ViewModels, resources, etc. Very difficult to find Api with ddd and web application integration, everybody only talk about the api and i am so confused.
So you want an MVC app with a separate API?
@@MilanJovanovicTech not really, i want know if i can have a web aplication in core that call api controllers, without MVC app
Hi Milan,
thanks for the video!
I have just one question though, why didn't you reference application project in infrastructure project?
(PS: I am new with clean architecture concepts)
Just missed to show it in the video, but you will need to have a reference regardless
Great video, I guess for the unit tests, it will be in another project right? in this case, a unit test project? what references from the other projects should have this unit test?
Unit test can reference all the other projects, not a big problem
Great Video simple and Clean :)
Good idea will be to record comparison of clean architecture approaches of ardalis vs jason taylor template.
One more idea maybe to record one without use of CQRS and MediatR in the Application layer.
keep up the good work
pozdrav iz Makedonije :)
Pozdrav 😁 I'll take a look at Ardalis, I've used Jason Taylor's architecture before
When would you want to use this design over modular monolith? In the end both seems to be more favored to bigger monoliths rather than small microservices.
Modular Monolith is a bigger concept than this. But each Module can use the Clean Architecture for example.
@@MilanJovanovicTech Would be a lot of projects in that single solution :) lets say you are using clean architecture and need to introduce some background processing like azure functions, for this its common you need to share code and entities. Would that function app reference the same app/infra project or how would you go about this?
Very nice!! It would be perfect if you add an example, including entity, dto, use case, EF, Logging and Http request
Covered most of them in other videos
can you share Links for the example plz @@MilanJovanovicTech
Have you or anyone implemented clean architecture in older versions of the .NET framework? The company I work for is still programming using this framework and it looks to me that we could also benefit from clean architecture also so I'd like to explore this possibility. It will be a plus of course if this has already been done to see how to approach this. Thanks
I can't remember the last time I used .NET Framework 😅 The biggest hurdle will be having a proper DI container to use. Everything else should be the same.
All you'd need is some DI library and you can have the same structure
Hi thanks for the video
Should I use this practice for .NET 8? Or now it's different with .NET 8?
It's fine in any .NET version :)
@@MilanJovanovicTech Thanks again.
I'm a junior developer and your videos are the best content that I saw for learning DDD and Clean Architecture.😘😘😘
Thank you for this educational video that you sent. Do you have an example of a website or a small project that can be implemented and that I can understand the concept of this method and standard for me to check, or have you made a training video on this matter so far? Thank you.
I have a course showing how to implement Clean Architecture on a practical project
@@MilanJovanovicTechWould you please send me the link of that video? Any help is appreciated.
Hi Milan, I've just started learning about clean architecture and I would like to clarify if the Domain layer is similar with Model classes?
Not really, it's a broader concept
Hi Milan,
can you suggest few good ways how to define the event flow between the 4 layers of CA in a diagram
What do you mean exactly?
@@MilanJovanovicTech I need to implement CQRS in another language. So i like to know which CA layer emits(i guess application layer) and which CA layers listen to the command and query. pls pardon my ignorance on CA on this aspect as I am trying on the same
I would disagree on a few points..
1. The WebAPI project is your presentation layer, you do not need a separate "Presentation" project.
2: Logging wasn't relevant to the video but it should be abstracted to an ILogger and it's implementation should be moved to the infrastructure project.
Obviously, these are just my opinions. Your videos are some of the best on RUclips for these topics.
1. Agreed, but this was about controlling direction of dependencies (if one needs it)
2. You can still use ILogger with Serilog
| Obviously, these are just my opinions
As are mine 😅 Most software engineering is opinionated.
Hi Milan! Thank you for the video. You pasted in the configuration for Serilog but there is a long line that is not visible towards the end. Can you share the whole code elsewhere please?
www.milanjovanovic.tech/blog/structured-logging-in-asp-net-core-with-serilog
Great Video! Can you record the insertion of the frontend (.cshtml) in the clean architecture template?
Maybe. I've been reluctant to touch MVC
Hi Milan, should Infrastructure and Presentation have project references to the Application? Theb WebApi project only reference thise two?
Yes
Thanks again Milan, I have a question, if you were to add SignalR to your project where would you put the setup? I mean hubs and stuff
Probably Infrastructure
Where are the optionsetups added to the iservicecollection? All in application so that infrastructure and persistence can make use of them in their dependency injection class?
The setup can be anywhere. But the options class needs to be where its used
Thanks! Btw for anyone who was wondering about thjs. For EF it provided a provider to get the service options when declaring the options config (Milan shows that in a vid). But I found if that wasn't available I'd declare the options config with the setup class then use the buildservicdprovided method then with that get the options class I just binded to.
Hey Milan I like your work.. thanks for sharing your valuable experience with us.. i have a simple question for you could you please explain a bit why you put separate class lib presentation project either you can add your controller on you webApi project that you added at the end...its confusing what to do with presentation layer then.. thanks your answer will be appreciated
I think I explained it in some video already
I was very confused when I heard that the presentation layer could be a REST Web API. In this case, which layer does my frontend built-in React that consumes this Web API belong to?
It could also be presentation layer - but I'm speaking strictly in terms of the context of a backend system
Hey Milan, first of all I like very much your videos :). Lately I also feel that the infrastructure indeed should be split in more parts like you did in your presentation: Intrastructure and Presentation and I have a question regarding this or at least I need confirmation for my thoughts :). For the case when I have an Api and a Cli built on top of my whole application then my infrastructure layer would be split in 3: Infrastructure (with core infra stuff), Presentation.Api, Presentation.CLI or? Thank you
I'd say the Infrastructure is irrelevant here. And the real question is Presentation - should we split it in two? If the entry points are different, and it looks like they are, then it makes sense
Hi, what is your approach to project setup for microservices?
I'll talk about it in a future video 😁
Thanks for sharing.
Do you going to continue evolve this application?
Over the next few videos, yeah. Take a look at the DDD Modeling one
Thank you for your useful tutorial. I have a question regarding the Presentation layer what is the difference between it and the WebApi project? and in case I have a project consisting of several presentations such as gRPC, WebApi, MVC, etc., what is the good way to handle all of them in a single project?
WebApi is the composition root, and it brings them all together at runtime.
Presentation is there to define the endpoints (entry points). You can move the Presentation into WebApi.
Hi Milan. Good stuff. Doesn't the Presentation layer project need to be AspNetCore as well? Or how to add controllers to a class library?
You can add the framework reference and it'll be enough
Hello! Thank you for video. I have a question - why dont you refer to application layer from infrastructure layer?
I just missed to show it in the video, in general you want to have that reference
@@MilanJovanovicTech thank you for your so fast answer! and while i was waiting that i get one more question where i can store logger service? in infrastracture or application layer? or i can create another project and store that here
@@DENDYTWOO I'd say Infrastructure
finally i land on the noob section please guide me into clean architecture. The Clean architecture and DDD series need to start from this vid😆 btw my VS not auto adding the using statemet :/ how do you do that ?
Check out my Clean Architecture playlist
Thanks but ideally, as expected in Clean Architecture of Uncle Bob : the Application Layer should be TECHNOLOGY AGNOSTIC, so in this layer : no dependency injection Tool, no Mediatr, and so on. All of this should go into the Infra Layer !
Might as well remove .NET while we're at it, just to be sure 😅
Hi Mr.Milan.
I can use the presentation as wpf
Yes
Thank you for your video. Best explanation I've found. I have a question. Is it correct to the WebAPI layer know about Infrastructure Layer? Some diagrams in the internet show that Application and Domain Layers only work with Infrastructure layer
Yes, that's fine
Within this example video, does the Presentation Layer Reference the Application Layer (MediatR Nuget was added into the Application project). ? Nice vid.
Yes, Presentation will reference Application
@@MilanJovanovicTech thanks, thought so.
I have two more layers. First is Data Access Layer or Repositories or Db layer and the second is Contract layer for request and response models
So you split Infra into Infra and Db? 🤔
@@MilanJovanovicTech exactly
Too many layers
hey milan!! I saw your serilog video and implement serilog in my project. its great.. but i need logs to print in seperate folders for each controller. can you please help me out or make another video about serilog with indepth configurations. thanks 👍
Is that even possible? 🤔
@@MilanJovanovicTech I searched about this and found few clues but didn't make it work... but its possible in NLog configuration
Should dependency inversion interfaces for Application layer live in Domain? Where should they go?
Most of them should be in the Application layer, and implemented in the Infrastructure/Persistence/Presentation
@@MilanJovanovicTech thanks for your reply, really appreciate it. I'm trying to wrap my head around this properly. Would use cases/ business logic that span several aggregates interfaces and implementation both sit in application layer? Should those go in the same folder? I'd like see some good examples of this.
Adding to this question would an entities IRepository be in a shared entity folder in the domain layer and then implementation be in the persistence layer? Then my use case services interface and implementation would use those repositories and sit in the application layer?
Very good content. Thank you.
Glad you liked it!
Thanks for the video, clear and direct, I liked the theme that you have applied, can you share the name please?
Visual Studio dark theme + ReSharper syntax highlighting
how can apply this on my frontend project with react or any framework?
No idea
I don't like CQRS and MediatR. I prefer repository pattern or hexagonal architecture. Do you have any better alternative?
Just use Services, not that much different
can you also do one for VSA?
Yes, I said I'm planning to 😁
Would also love to see a Vertical Slice example
Very Useful
Glad you think so!
Good explanation
Thank you 😁
Shouldn't logging be configured inside the infrastructure layer ? I've seen CA aproaches using Serilog this way. Is it more optimal to configure it inside the API layer on .NET latest versions?
I find it simpler to configure it from Infra, that's all
Hi @MilanJovanovicTech, I know this is an old video, but I'm learning about minimal APIs in .Net 8 and clean architecture. I have all my clean architecture structure inside the web API project and I want to separate it into the layers in this tutorial (a project for each layer of the clean architecture). I was able to separate the structure into projects and I'm trying to add the EndpointRouteBuilderExtensions class into the infrastructure layer, but i cannot implement the IEndpointRouteBuilder interface inside the infrastructure project, as this project is a class library project instead of a webapi project. Is there a way to add a reference inside the Infrastructure project in order to get the IEndpointBuilder interface and use it?
Yes, add this to your .csproj file:
@@MilanJovanovicTech Thank you so much, it worked fine!
Nice content mate
Much appreciated
KING
Thank you sir! Have this 👑👑👑
I have a question...
I want to controllers in presentation layer, how to do?
Explained it here I think: ruclips.net/video/tLk4pZZtiDY/видео.html
What if some of the domain models are linked to the IdentityUser like navigation property, while IdentityUser is a part of "Microsoft.AspNetCore.Identity.EntityFrameworkCore", what is the workaround for that? does it violate the Clean Architecture by just adding that?
Leave Identity out of the Domain. I'll try to tackle that topic in a video
@@MilanJovanovicTech yes this is the approach I took; kept it as a separate module and context. All working well, there are cases where Application needs to know the identity users id. Would be interested to see how you would approach this.
@@chrismoutray9206 How I did it in the past is store the IdentityProviderId on the User entity, but leave the other IDP things out of it
Nice video, thanks a lot
Glad you liked it!
Hi, Milan
Could make a video on how to do logging/caching at method level
Using dynamic proxy.
I'll first have to learn what a dynamic proxy is 😁
Does not Infrastructure project need dependency on Domain? How would you persist records without domain layer referenced in Infra/persistence project?
It has the Domain reference from the Application layer
@@MilanJovanovicTech it means you are referring Application layer in the Infrastructure/Persistence project? Maybe I missed in the video.
You mentioned that the API doesnt need to import the domain layer, because it will implicitly get it from the application layer, what do you mean by that, when the application layer doesnt hold the domain logic. Was this something you did not meant to say, or could you elaborate on what you mean. Right now my API needed to import also the domain layer, since thats where the models, exceptions etc are stored. But if you have a way to get to the domain from application, I am all open minded.
Transitive reference.
Application -> Domain
API -> Application, and by extension API -> Application -> Domain
For that classes Presentation project ?
Separating the executable from the endpoints. So controllers, minimal Apis, view models.
It will be great if you maybe implement 1 entity for that architecture(CRUD)
Just wanted to focus on the structure here
Thanks a lot for this greate video. I have subscribed, but I don't understand why you created a presentation layer then the api layer?
To separate endpoints (public API) from DI logic, more control over what Presentation can reference
Very useful.
Glad it was helpful!
What if there are multiple apis or web projects？
Then you're doing microservices?
@@MilanJovanovicTech Not microservices, but an api and a management backend web, I think most api should have a management backend it
Why would the WebApi (UI layer) have a reference to the Infrastructure layer?
Wiring up DI for one
you did not add any references from the infrastructure or presentation layer. Those should reference the domain layer...?
Yeah, got a little carried away in the second part of the video 😅😅
Should the Infrastructure be dependent on the Application?
It is fine
When writing for example a microservice or another type of project when all the business logic can only be exposed by webapi calls: I like handling all the validation as a middleware for webapi controllers or minimal APIs. That way your services/CQRS handlers and even domain classes do not need to be populated with validation and checks like the length of the email, etc
Agreed, that's also the approach I use
Hmm... probably should as a base set up a test project with Architecture/Layers tests.
Then, yea make it a template. :)
That's a wonderful idea!