Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Decision: Which ORM should we use? #235

Open
goldbergyoni opened this issue Sep 29, 2022 · 3 comments
Open

Decision: Which ORM should we use? #235

goldbergyoni opened this issue Sep 29, 2022 · 3 comments
Labels

Comments

@goldbergyoni
Copy link
Contributor

goldbergyoni commented Sep 29, 2022

Like any other decision, we wish to have a discussion and always compare the various options here

Which Node.js ORM should use? What important dimension should be evaluated?

@rluvaton
Copy link
Collaborator

rluvaton commented Oct 3, 2022

Let's take a step back and ask, do we even want an ORM? What about query builder?

If we do decide to go with ORM than my important dimensions IMO are:

  1. Performance
  2. Security to help protecting from SQL injections
  3. Support for multiple DBs (optional not required)
  4. Migration support
  5. Type support (Maybe)

@aagamezl
Copy link

I like the ORM option more than a Query Builder and my vote goes to Prisma.

@koyuncuoglum95
Copy link

koyuncuoglum95 commented May 27, 2023

@goldbergyoni, I'd suggest you to use mongoose and Prisma.

Mongoose:
1.) provides a straightforward
2.) schema-based solution to model your application data
3.) along with built-in type casting
4.) validation, query building
5.) business logic hooks

Prisma:
1.) Strongly-Typed API
2.) Auto-Generated Client
3.) Declarative Schema Language
4.) Support for Complex Queries
5.) Database Migrations
6.) Rich Data Modeling
7.) Developer Experience
8.) Support for Multiple Databases

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants