---
title: "Discussion on \"Advanced project setup with Nest.js and Typescript\" | Hashnode"
description: "Discussion on \"Advanced project setup with Nest.js and Typescript\". Tips and tricks for Linting & Co. that go beyond the default scaffold"
url: "https://hashnode.com/posts/advanced-project-setup-with-nestjs-and-typescript/661d21b44b8894528066e727"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Advanced project setup with Nest.js and Typescript](https://agilecoding.io/advanced-project-setup-with-nestjs-and-typescript?utm_source=hashnode&utm_medium=feed)

Tips and tricks for Linting & Co. that go beyond the default scaffold

Apr 15, 2024 · 8 min read · agilecoding.io  
Read the article

-   [#nodejs](https://hashnode.com/tag/nodejs)
-   [#typescript](https://hashnode.com/tag/typescript)
-   [#linting](https://hashnode.com/tag/linting)
-   [#eslint](https://hashnode.com/tag/eslint)
-   [#nestjs](https://hashnode.com/tag/nestjs)

## Written by

[Klaus Lehner](https://hashnode.com/@Klu2)

@Klu2 · Vienna, AT

  
[View profile](https://hashnode.com/@Klu2)

Developing people, organizations and software

Self-employed advisor for a holistic view on the whole software engineering process. Developing people, developing organizations, developing software. Still passionate coder.

## Responses 2

Markdown supported · ⌘↵ to post

[DK](https://hashnode.com/@DKirschDK)

[Aug 26, 2025](https://hashnode.com/posts/advanced-project-setup-with-nestjs-and-typescript/661d21b44b8894528066e727/comment/68ad11b232370e543d65d18d)

Hi Klaus, I enjoyed your articles on Nestjs and have been curious about using it for a while now. I wanted to ask what is you impression nowadays, after having used it some time and if you still continue with, or would consider using it if the need arises. Thanks!

[Ezequiel Regaldo](https://hashnode.com/@Swarow)

[Aug 30, 2024](https://hashnode.com/posts/advanced-project-setup-with-nestjs-and-typescript/661d21b44b8894528066e727/comment/66d1d26f9a966ceb2271fa37)

Hi Klaus, first of all, welcome to JS/TS world ! Please let me suggest something to your code, if you're using multiple cores, for each 4 cores, spawn a node cluster to improve significantly the ammount of requests. For example:

/////// File : cluster.service.ts

import _as cluster from "cluster"; import_ as process from "node:process";

const numOfClusters = 4; // Im using 16 cores @Injectable() export class ClusterService { static clusterize(callback: Function): void { if (cluster.isMaster) { console.log(`MASTER SERVER (${process.pid}) IS RUNNING`);

for (let i = 0; i < numOfClusters; i++) { cluster.fork(); }

cluster.on("exit", (worker, code, signal) => { console.log(`worker ${worker.process.pid} died`); }); } else { callback(); } } }

/////// File : main.ts

import { NestFactory } from '@nestjs/core'; import { AppModule } from './app.module'; import { ClusterService } from './cluster/cluster.service'; import { FastifyAdapter, NestFastifyApplication } from '@nestjs/platform-fastify';

async function bootstrap() { const app = await NestFactory.create( AppModule, new FastifyAdapter() ); await app.listen(3000, '127.0.0.1'); } ClusterService.clusterize(bootstrap)

/////// Conclusion :

I tested this in bare metal and docker containers and i get 20% ~ 40% more requests than spring boot equivalent. Im really surprised how nodejs can handle too many requests with minimal effort