Royi Benita @ NodeTLV 22 - Clean Node.js Architecture -With NestJs and TypeScript
HTML-код
- Опубликовано: 6 сен 2024
- NodeTLV 2022
www.nodetlv.com
Israel's Annual Node.js conference
Powered by EventHandler and Node.js-IL
Clean Node.js Architecture -With NestJs and TypeScript
Node is not an opinionated framework and you can find yourself easily maintaining a tightly coupled system that is depended on the frameworks it uses.
Implementing Clean Architecture in your node application using NestJS can put you on the right track for creating a robust and loosely coupled system.
As stated by Robert C. Martin- “Your architectures should tell readers about the system, not about the frameworks you used in your system"
Royi Benita
Full Stack software developer with 13 years of experience and a deep knowledge in web and mobile platforms, focused mainly on web distributed systems.
Royi has been working for the past 2 years at Fiverr in the localization team, building node and react Microservices. He is also an experienced public speaker.
Read more about Royi’s work here:
/ royibeni
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. 😘
nice talk, thank you
this video should DEFINETELY receive more views!!!
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
Great talk! Thanks.
Very well explained, thanks.
excellent explanation and great examples🥰
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.
nice video :)
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.