Over 2 years since I came across clean architecture and by far the best and clearest explanation with sample code implementation that I have understood without having to do side googling. 😘
Its basically exactly the same structure as Angular. React is farly not as opiniated as Angular, and that is the reason why its so robust and will prevent people from trying to be "cleaver" and be able to get results when not really understanding how it actually works
Can someone please explain why it is necessary to create such entities as usecases if there are services in which we describe business logic in the same way, and what is the difference between them? Or am I misunderstanding something?
It’s called a facade. Services change, Business Domain and its problems and goals change, but often independent of another. This decouples them. I.e. a user can now be friends with other users. The service for logins may need to support more login types.
Can we stop calling DIP, Clean architecture please. Nobody mentions the key difference of an interface adapter nor do they mention the added principles on top of CA.
Late reply, but I believe what the OP is suggesting is that by referring to dependency inversion principle (DIP) as Clean Architecture (CA), one would be omitting many other principles that are encompassed by clean architecture. Like single responsibility principle, open/closed principle, etc. Look up SOLID design for more information.
![[#2024MAMA] G-DRAGON - 무제(Untitled, 2014)+POWER+HOME SWEET HOME+뱅뱅뱅+FANTASTIC BABY | Mnet 241123 방송](http://i.ytimg.com/vi/Ox29z5Nf1Uk/mqdefault.jpg)
Over 2 years since I came across clean architecture and by far the best and clearest explanation with sample code implementation that I have understood without having to do side googling. 😘
this video should DEFINETELY receive more views!!!
nice talk, thank you
Great talk! Thanks.
Very well explained, thanks.
excellent explanation and great examples🥰
nestJs is more like angular than react :)
Its basically exactly the same structure as Angular. React is farly not as opiniated as Angular, and that is the reason why its so robust and will prevent people from trying to be "cleaver" and be able to get results when not really understanding how it actually works
nice video :)
Can someone please explain why it is necessary to create such entities as usecases if there are services in which we describe business logic in the same way, and what is the difference between them? Or am I misunderstanding something?
It’s called a facade. Services change, Business Domain and its problems and goals change, but often independent of another. This decouples them. I.e. a user can now be friends with other users. The service for logins may need to support more login types.
Can we stop calling DIP, Clean architecture please. Nobody mentions the key difference of an interface adapter nor do they mention the added principles on top of CA.
Sorry for the ignorance. What do you mean ?
Late reply, but I believe what the OP is suggesting is that by referring to dependency inversion principle (DIP) as Clean Architecture (CA), one would be omitting many other principles that are encompassed by clean architecture. Like single responsibility principle, open/closed principle, etc. Look up SOLID design for more information.