The Clean Architecture | Simply Explained | .NET Core

Practical Software Architecture Solutions from the Legendary Robert C. Martin (“Uncle Bob”) By applying universal rules of software architecture, you can dramatically improve developer productivity throughout the life of any software system.

00:00 Introduction To Video
00:17 Need of Clean Architecture
00:47 Concept Of Clean Architecture
01:58 Dependency Flow
02:49 The Domain Layer
03:14 The Application Layer
04:43 The Infrastructure Layer

We upload videos every Sunday.

Background score attribution:
Creative Commons Attribution 3.0 Unported License

[hheeaaddhunter]

Are you sure that no classes are defined in the Application layer and only interfaces? Because in other videos they say that you have your main logic in the application layer.

[PrashantRai-nl]

finally my search is over here! Thanks bro

[hatimjohar]

Amazing explanation, understood in few minutes content worth of pages with clarity. Thank you

[HugoFlux]

Here something for you to think about. Having a reference from infrastructure to Application and Domain you would be able to inject a high level bussiness class into the infrastructure.
I would keep the infrastructure low level by only doing 1 interaction and mapping and forcing the other logic to be inside a business service.

[sheshikanthkotte]

In infrastructure structure layer you are implementing repositories i.e: operations with data base but you need to call repository method in services that is application layer, here application layer need to have dependency with infrastructure layer right? Then it is likeenot following clean architecture

[victordfb]

I think the example throughout the video didn't stay on track with the initial proposal of the business domain. I didn't see the car stoping on red sign and saving state on database. But the most important think I've noticed, it seems the way the solution goes, the business logic will be scattered around application and infra layers while the clean architecture proposes to keep the business logic inside domain layer and use infra/application to separate things like how to db access from the domain. I think the example is misleading the clean architecture understanding

[keyranjoshi]

Speed, Animation content love all things about channel. Hates of for your efforts and time word is not enough. very good work ❤❤❤👏👏👏

[imadayoub]

Excellent brief. Thanks a lot. I have subscribed.

[veereshsuryac]

Wow really clear and neat explanation with animations. Thank you very much for the videos. please do upload such good content. Hats off to you people.

[kotaclassesIglas]

Greate
i clicked on subscribe button after 30 second

[reddy_gariammai]

Have you made videos on the topics mentioned in this video, like CQRS and mediatR patterns, fluent validators?

[ChrisAthanas]

The animations, although cute, simply add to the confusion of this video

[godfather]

Domain layer must not depend on any other layers

[ifstatementifstatement]

Great video! Is clean architecture applicable for developing a video game also?

[TheMaKasss]

This video is not a good example, it is misleading.

[adamgoldsmith]

The domain layer should contain the core business logic, things that the program is emulating (like a DDD entity and aggregate), then the application layer should be the application specific logic.

I stopped watching after you defined the domain layer, as its obvious that you have not read the clean architecture book

[ChrisAthanas]

Why always cars?

How about a store or a real world use case?

Cats just confuse everything

[wanys]

you are so fast why you harry you looks like you just reading

[ivanramirezmejia]

One of the worst videos about this topic

[DarshanaHashendra]

too simplified and wasting time of users, please prepare proper content instead of basic explanation