SLanberg
commented
9 months ago Brief comparison between Node.js and Nest.js:
Architecture:
Nest.js follows the modular and scalable architectural pattern known as “Dependency Injection” and “Decorator” syntax. It encourages the use of TypeScript and provides a structured way to organize code using modules, controllers, and services. Node.js, on the other hand, is a runtime environment that executes JavaScript code on the server side.
Features and Abstractions:
Nest.js provides a rich set of features out of the box, such as built-in support for modules, middleware, dependency injection, and decorators. It also offers powerful features like automatic route generation, validation, and serialization. Node.js, being a runtime environment, provides low-level APIs for networking, file system access, and other system-level operations. It allows for more flexibility and control but requires manual implementation of higher-level abstractions.
Scalability and Performance:
Nest.js leverages the scalability and performance of Node.js by providing a modular architecture and built-in support for asynchronous programming using Promises and async/await. It allows for efficient handling of concurrent requests and can scale well for high traffic applications. Node.js, being a lightweight and non-blocking I/O runtime, is known for its high scalability and performance characteristics.
Use Cases:
Nest.js is well-suited for building complex, scalable, and maintainable server-side applications, particularly in the realm of enterprise and large-scale projects. It combines the benefits of TypeScript, architectural patterns, and a robust framework to provide structure and productivity. Node.js, on the other hand, is a versatile runtime that can be used for a wide range of applications, including web servers, real-time applications, microservices, APIs, and command-line tools.
Goal:
I need to handle many requests from the user base up to 100k+ users in comparison Nest.JS has more advantages for mine goals, and has a better built-in architecture. Node.js can be good to support legacy code from the potential employer.
I want typeorm, concise logic using UML for the database.
Check what gives Telegram at the user's registration prepare statistics gathering of the player's account.
Since the Node.js choice was dictated by the strict deadline and I'm not satisfied with how it is build I want to see work that is on the level of our previous production projects.