I can do the programming part but please tell me how I create images like the one at the beginning so my coworkers don't bother me.
That’s not only Clean Architecture, it’s also Hexagonal Architecture and also Onion at the same time
I'm thinking about combining microservices arch with clean arch in a way where the main website files including entities and repositories would be based on clean arch, and then that infrastructure layer would basically be my microservices. Would that idea be any good?
What about relationships between entities? Domain layer?
What do you think about Onion Architecture as compare to clean ?
Milan thanks for all your vids! I am curious about the answer to my question. Bookify is a nice and simple project where you have tons of folder for every thing in the process and I understand why. My question is for a huge serious project with tons of features and entities, should I keep creating folders 📁 for pretty much everything? I am just curious because of the answer is yes then I will end having almost the same amount of folders as for each .cs file we I have.
I think Onion Arc. More complex.
why sometime i see repository interfaces in the domain? it wasnt suposed to be on application layer?
How do i handle dependency injenction between the layers?
Clean!!!
The video has a different structure rhan the short . why add a presentation class ? It has no purpose. How will you call it inside the web api ?
Where do you put HttpClient for consuming external APIs? Application?
@Dpaz2009