Recently, I had a chance to work with Angular and liked the class design in the Angular project (Disclaimed: I worked with React and Vue before Angular). It has a good structure for enterprise applications.

I was wondering if there is something similar for the Node backend framework. And finally, I found NestJS. But NestJS is not Angular for the backend, it has many exciting things for building enterprise backend and provides many cool features. And the last thing, if you love Dependency Injection (DI), you should take a look at NestJS. Let's go deeper!

What is NestJS?

NestJS was built by using good design patterns (DI is one of them) to provide a level of abstraction above these common Node.js frameworks (Express/Fastify), but also exposes their APIs directly to the developer.

For more information about NestJS, you can take a look at their documents.

What do I love?

• It uses Typescript. As you know, Typescript provides strong static type checking for our Javascript application, so we can confidently deliver to production. That is the big advantage of a NodeJS framework.
• The modular pattern is where we can split our application into modules. The benefit of that, we can create shared modules to use across many applications. It's like we play LEGO.
• Nest provides many production-ready features that we can include quickly into our backend. From the docs, you can see some modules such as Authentication, Authorization, Database ORM, Guards, GraphQL, Queue, CORS, CSRF, etc. Many features that you can integrate into just minutes or hours to make it work.
• For each feature, Nest allows us to choose what we love. For example, for Database ORM, we can choose TypeORM, Sequelize, Knex.js, etc, so we can apply what we have experience.
• Nest has a cool CLI (likes Angular) where we can generate different kind of schematic. The best one is CRUD generator, it will generate all resources (module, service, resolver, controller, data transfer object, etc) that we need for an entity.

What I don't like?

Nothing for now because I only spent one month in NestJS but I believe each framework will have their limitations.

As you may know, I started the "6 products in 12 months" challenge. Unfortunately, the first product is going slow because I was not clear enough about the product, that was my fault.

I'm slightly disappointed because the speed is so slow, but I learned sometimes we should be patient with the plan because the good things will take time.

I have some product ideas, but they're related to third-party integrations. Hence, I decided to take 2 months to build the third-party integrations platform that I can use across upcoming products and can be open source soon.

Maybe I can't complete 6 products in 12 months, but I will try my best. At least right now, I'm happy with my plan.

Five years ago, I started working as a freelancer to get sustainable finance for my family because I got married and have one beautiful daughter, I also have to take care of my parents.

Although I have a good income and a nice company to work with, but I always want to start something on my own. Everyone has a passion and a dream.

I founded my startup in the past before I started my freelancing job, but it failed. I always want to try again. My problem is I’m working 40 hours per week to earn money, I don’t have much time to focus on the products, so I only can focus on small things.

I tried on many ideas but can’t finish one of them because sometimes, I was thinking too big, and the plan was growing bigger, so I can’t complete them.

So I would like to accept the “6 products in 12 months” challenge because it will help me to solve some of my own problems such as:

• Start small: I have to think about how I can complete product development in 1 month and spend one month for marketing to validate. So the product should be small and be focused.
• Always finish: We should finish anything that we started. So although the product can go bad at least I can finish what I planned.
• Focus: Because I limit 2 months for each product, I will try my best to grow a product in that time. If it can't grow, I will keep it growing organically and try another product.

After 12 months, I will look at a promising product and focus on that. The challenge will be started on 1 June 2022. LET’S GOOOOOO!