MikroORM VS Objection.js

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/

Objection.js is a SQL-friendly ORM for Node.js that supports various relational databases, including PostgreSQL, MySQL, and SQLite. It provides a flexible and expressive query builder. Objection.js is known for its expressive syntax, allowing developers to build complex queries easily. It supports eager loading, transactions, and migrations.

I don't think there's a best per say, but we did recently use Objection on our project. Did the job well, only issue is there's no constructor for the DB Models but it's just something you work around (https://vincit.github.io/objection.js/)

If you aren't using TypeScript I'd very much recommend Objection.js, I've used it multiple times and no complaints so far. You can pass raw SQL queries to it as well so I'm sure it would be a good fit for your project!

I'd also like to point out objection js is no longer actively maintained. I'm going to switch my work's codebase from it eventually because of it.

You should look into Objection.js. IMHO using that will make your life much easier as it seems you are trying to reimplement it's features in this sample code.

Next, let’s set up the database for our newly created Nest application. I’ll be using PostgreSQL, but you can use any of the databases Knex supports. To interact with our database, we’ll be using Objection.js, which is an ORM for Node.js built on top Knex. For this tutorial, we’ll be using Nest Objection, a Nest module for Objection.