Clean architecture with nodeJs express : practical example in node.js 

Thank you for your kind words. Stay tuned to our channel and join our discord channel for Job offer announcements and updates. Cheers!

Thank you for your appreciation. Some time it's not easy to cover all the edge cases. But I will take a note on your suggestion. Cheers!

My pleasure!

normally most of the companies follow Clean Architecture and later stage cover the test cases with min 80% threshold but TDD is just to understand how things has to handle in learning stage. In real life its a bit time consuming for sure. If you learnt it you are good to go.

Glad it was helpful!

I'm glad the tutorial was helpful for you! Cheers!

Thanks a lot my friend! Wish you Happy new year!

Hey Thank you for writing! Certainly I will cover that in part 2. As soon as we covered this series Elastic Search Functionality.

Thank you so much 😀

Thank you for writing. In javascript and typescript bind returns a new function with the bound "this". Example: in our case router.post("/products", controller.onCreateProduct.bind(controller)); Here bind method is used to ensure that the onCreateProduct function is called with a specific this context, which is the controller object in this case. The bind method creates a new function that, when called, has its this value set to the provided argument. In this example, controller.onCreateProduct.bind(controller) creates a new function where the this value inside onCreateProduct will refer to the controller object.This is commonly done in the context of setting up routes in web frameworks, where you want to ensure that the controller methods are called with the correct context. Hope it will help! Cheers!

Yes you can. But you need to understand how it works at least while we are facing coding interviews the framework will not help to convince interviewers :)

Hi Thanks, All the knowledge you have gain so far till 42:00 is the manual dependency injection process with transparency where we can understand how the mechanism works and you have full control on it. Now the big overheads are it's manual and you need to write lot of boiler plate codes to get the job done. So Inversify is a Dependency framework that is helping us to reduce all manual work and make sure instances are used efficiently for optimal memory usages. Here is why and which one to use: Inversify: Use it when working on larger projects, where dependency management could get complicated. It also fits well with TypeScript-heavy codebases, where decorators and metadata provide clear advantages in terms of type safety and cleaner code. Manual DI: It works well for smaller or simpler projects, where adding an entire framework for dependency injection may be overkill. It's also useful for learning or when the project does not need the complexity that a DI framework brings. Cheers!

@@codewithjay Thanks Jay. You are the best! I watch your videos and will renew my membership again soon.

They are not same. It is sharing common principles like separation of concerns in layers, and clean dependency pattern, Inversion of controls etc. Each architecture has it's own emphases and implementations based on use cases. Overall if you at least know one of them you are good to go. I will release some videos in future based on these concepts.

@Jay you response on this will be appreciated

Hey thanks a lot for writing! TBH there are no such silver bullet points as Industry best practices. But it's depends on your project requirements and how your team decide what to follow. I would recommend to use some ORM to save your time and complexity. Behind the scene all ORM is used raw sql only and it gives flexibility to deal with Database queries and execution using high level abstractions. You can use TypeORM or Prisma that is widely used in NodeJS ecosystem. You can use NestJS that's an wonderful framework! But not recommended for simple requirements and specially when we are not dealing with Microservice or big project requirements. But if you really want to structure project without put your hands to create structure like in our current video. You can go with NestJS. Note: We have not implemented any ORM on this Episode just for shake of time but we have already implemented ORM (Prisma) for our this series you will see very soon in coming videos. Cheers!

please follow the answer!

Hi thanks a lot for your opinion! It's up to you how you organize your codes but in this project we tried to decoupled by keeping essential layers only as per the principal. If you understood the concept you can minimize your code accordingly. In this case if we not spreading the codes to layers it belongs to and not injected dependencies properly to perform the operation in the loosely couple way then it will be not meaning full to implement Clean architecture anymore. Cheers!

To write an entity validator in TypeScript while avoiding direct coupling to specific node packages, you can adopt an abstraction approach. This involves defining your own validation interfaces and using a strategy pattern to apply various validation implementations. In our case we are using AJV and typeBox with generic to disconnecting the coupling.

@@codewithjay Thank you !

Hi, Thank you for writing. Here we just want to give an overview of how clean architecture works by keeping loose coupling of the layers and dependencies. It's up to you to follow the pattern or maybe you can shape it as per your application needs by revoking extra layers. You do not necessarily need to use interactors in the case of Javascript it is out of the question. In functional programming, you can get rid of it and hook up with your dedicated function to replace the functionality. You can watch our latest episodes for references. Cheers!

Thank you for writing and your opinion. We are focusing on to understand the mechanism only not the a framework. You can use NestJS if you know how it works behind the scene. Note: This tutorial series made based on viewers request how to build such system using NodeJs not NestJS.

It's not about ended with Object Oriented Programming! It's about the removing dependencies and utilize of layered architecture that Domain and Application business logic not to tightly dependent on framework and drivers etc. If you understand the concept correctly you can utilize it on functional programming as well. We following Class pattern just to make people understand easy way. If you are following this series you will see the functional usages with clean architecture in future lactures. Cheers!

You can add it in the route file example: // Authentication middleware (example) const authMiddleware = (req: Request, res: Response, next: NextFunction) => { // Placeholder for actual authentication logic with jwt const isAuthenticated = true; // Replace with real authentication check if (!isAuthenticated) { return res.status(401).json({ message: "Unauthorized" }); } next(); }; // Apply middleware to all routes router.use(loggerMiddleware); or if specific endpoint needs authentication you can use like below: router.post( "/products", authMiddleware, async (req: Request, res: Response, next: NextFunction) => { try { const { errors, input } = await RequestValidator( CreateProductRequest, req.body ); if (errors) return res.status(400).json(errors); const data = await catalogService.createProduct(input); return res.status(201).json(data); } catch (error) { next(error); } } ); Hope it will help you :) Cheers!

It's up to you how you organize your files. Only matters to follow the principal and Enterprise and Application business rules should not affect when we change UI and framework along with Data Access Layer.

You can use one as per your convenient. Cheers!

What do you mean by saying "generator", could you explain it?

Something like plopjs

Yes, You can use NestJS that's an wonderful framework! But not recommended for all the use cases. Example some times its overkill when we have simple requirements and specially when we are not dealing with Microservice or big project requirements. But if you really want to structure project without put your hands to create structure like in our current video. You can go with NestJS. Cheers!

Yes this series is based on Kafka & Elastic Search, Prisma and Clean Architecture!

JetBrains Mono