Digging into NestJS

This Blog Post was originally published on the platform "writelier" (formerly "co-writers" and "200wordsaday"). Sadly the blogging platform was discontinued. I downloaded all my blog posts and prepared them to be republish them here.

The company I work at finally decided that we have to start rewriting the software I am working on. Some articles where I laid out a few details can be found: here, here, and here.

The last project turned our relatively good and so we got the go on the larger rewrite. But before we can start programming, planning has to occur.

Currently, two Major Milestones are laid out by our Department Manager. My task the last days and the next days is to evaluate the necessary server parts to achieve the milestones. And potential Server Frameworks we could use.

In the new product I mentioned in the Typescript article above, I'm using KoaJs. In the upcoming new product, we will use NestJS.

I looked into it the whole day and have to admit, I'm really impressed by the possibilities.

It has many built-in functions you don't need to reimplement over and over again. It looks like they really thought through the whole thing.

When I first tried a few things with it, I thought it was just another HTTP-Framework like Express or Koa, but it feels like express (well, it is based on it) on steroids or something.

They include WebSockets (which we need), Database stuff (which we need), caching (which we need), authentication (which we need). Finally, a nodeJS framework that is made for large applications.

Subscribe to Philipp Haidenbauer | Blog

Don’t miss out on the latest issues. Sign up now to get access to the library of members-only issues.