Switch my backend to Nest.js

Switch my backend to Nest.js

When starting a new project, one of the important things to cross in your to-do list is the decision of which stack are you going to use for it.

In the last years, plenty of new frameworks have appeared in what I like to call the Framework Era. There is a framework for almost everything. And you know, the more options you have, the harder to decide on one.

My last web projects have transited, in the backend, between the two most famous Node.js libraries (although there is debate about whether we should consider them something more than libraries): Express and Fastify.

The first one is the old known buddy. With an enormous community behind, but with a very slow development.

On the other side of the ring, Fastify is a newer solution, focused on performance, which includes some pretty good features out of the box.

But as it happens with React.js, when a technology becomes used, people start to develop layers on top of that technology to ease the path to newcomers.

That is the case of Nest.js, a framework for the backend which can have Express or Fastify below, being able to abstract most of the difficult tasks required in both libraries to accomplish your backend goals.

Let's move

So that is the rationale. As I have worked with Express and Fastify and I have the minimum knowledge required to try new challenges, I believe it's time to switch to a more complex solution.

The following side-projects in my queue which require server-side development will be coded using Nest.js and I will try to document my journey with this Framework in a series of chapters in this blog.

Wish me luck!