nestjs-typegoose VS MikroORM

As much as I don't like to use it, there are people who decide that NoSQL and MongoDB are the way to go for their application. Before v7, Nest didn't provide it's own decorators for a mongoose integration, and developers had to use the standard schema approach. While there's nothing wrong with this, it definitely does bring in some pain points when it comes to types and DTOs, so a SchemaFactory was created to allow developers to keep using classes to define their mongoose schemas. This works pretty well, but does admittedly lack some features, like virtuals and static methods. These can be added to the generated schema, but Typescript will not know about them. I usually suggest people use nestjs-typegoose instead of Mongoose/Typegoose integration with NestJS.

In my usual NodeJS tech stack, which includes GraphQL, NestJS, SQL (predominantly PostgreSQL with MikroORM), I encountered these limitations. To overcome them, I've developed a new stack utilizing Rust, which still offers some ease of development:

https://www.npmjs.com/package/mikro-orm - 44 issues

Mikro-ORM is a TypeScript ORM that focuses on simplicity and efficiency. It supports various SQL databases and MongoDB. Mikro-ORM is known for its simplicity and developer-friendly APIs. It provides a concise syntax for defining data models and relationships, making it easy to use.

I found MikroORM [0] to be quite reasonable if you're in the TS ecosystem already. It was also easy to do custom, raw queries, and really just felt like it wasn't in the way.

[0] https://mikro-orm.io/

It also does code generation into its own module, so good luck with hoisting in a monorepo where you want multiple independent prisma schemas. MikroORM[1] is a much better alternative to Prisma in my opinion but any ORM carries some form of baggage.

[1] https://mikro-orm.io/

More about v6 development can be found here.

I recommend looking at https://mikro-orm.io/