aqueduct VS Nest

Why not just find new maintainer for Aqueduct or Angel ? Or pull out a reusable ORM package from them ?

Saw this about Aqueduct also losing support as it is tough to move to null-safe. https://github.com/stablekernel/aqueduct/issues/917#issuecomment-783700669

From - https://github.com/stablekernel/aqueduct/issues/917

https://github.com/stablekernel/aqueduct/issues/917#issuecomment-783700669

Agreed, it is also more on brand with the website to use Dart for our backend. As for graphql support, aqueduct afaik currently does not have graphql support as per this issue. If we are to use graphql, angel looks like a good option. Otherwise we have to fallback to REST instead.

Framework updates from NestJS, Deno, and Laravel.

https://nestjs.com - the official website of the framework

NestJs

You'll never be able to learn Angular, as it forces you to write only TS code, the same case with the loopback 4. NestJS primary language is TypeScritpt and they also provide support for JavaScript. Following are the words of NestJs

I mean, this really depends on what you're looking at.

Here's a sample from the MongoDB client: https://github.com/mongodb/node-mongodb-native/blob/main/src...

Here's a sample from Storybook: https://github.com/storybookjs/storybook/blob/next/code/core...

Here's a sample from Prisma: https://github.com/prisma/prisma/blob/main/packages/client/s...

Here's a sample from Cal.com: https://github.com/calcom/cal.com/blob/main/packages/core/Ev...

It's rather the specific use case that determines the style of the code that's written. In the examples above, there's no need for the teams to choose JavaScript classes and inheritance to model the logic, yet it likely better fits the programming model of those modules.

Look at Nest.js as well: https://github.com/nestjs/nest/blob/master/packages/core/rou...

The whole codebase of Nest.js looks an aweful lot like Spring or ASP.NET (controller syntax) probably because there's a lot of crossover in terms of what APIs need at scale.

It just so happens that most use cases for C# and Java favor applications at a larger scale. Another key difference being object scope and lifecycles -- something that rarely comes into play in the generally single-threaded Node runtime. This being one of the key reasons why dependency injection is a thing in C# and Java land.

Nest.js: A comprehensive framework for building large-scale applications. Its core follows the MVC pattern and makes heavy use of decorators.

The frameworks we will be looking at are: Nest, Elysia, Encore.ts and Hono.

To do this effectively, it’s often helpful to use a microservice framework. But choosing the right framework that natively supports microservices can be challenging. In this article, we are going to take a look at Encore.ts and Nest.js as the two relevant alternatives, since they both natively support microservices architectures and TypeScript.

https://nestjs.com - the official website of the framework https://nestjs-mod.com - the official website of additional utilities https://fullstack.nestjs-mod.com - website from the post https://github.com/nestjs-mod/nestjs-mod-fullstack - the project from the post https://github.com/nestjs-mod/nestjs-mod-fullstack/compare/ec8de9d574a6dbcef3c3339e876ce156a3974aae..414980df21e585cb798e1ff756300c4547e68a42 - current changes https://github.com/nestjs-mod/nestjs-mod-fullstack/actions/runs/11523894922/artifacts/2105784301 - video of the tests