@hatimjohar8911
Amazing explanation, understood in few minutes content worth of pages with clarity. Thank you
@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.
@shahzadahmad-vg2ou
Thank you for the great video.
@adelalmansoury
Great Work
@keyranjoshi10
Speed, Animation content love all things about channel. Hates of for your efforts and time word is not enough. very good work ❤❤❤👏👏👏
@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.
@kvelez
Great video, thanks.
@kotaclassesIglas
Greate i clicked on subscribe button after 30 second
@indikanadun475
cool and excellent demo..!
@djscratchnsniff
thanks for the video
@finwwwfinwww4669
you are awesome
@sheshikanthkotte2313
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
@veereshsuryac9121
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.
@imadayoub5237
Excellent brief. Thanks a lot. I have subscribed.
@ShivamJha00
Thanks.
@TheMaKasss
This video is not a good example, it is misleading.
@mohdotnet
Good video but the infrastructure layer is that not for external things like databases rabitmq file system stuff etc ?
@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
@adamgoldsmith310
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
@PrashantRai-n3l