Alternatives to Objection.js logo

Alternatives to Objection.js

Sequelize, TypeORM, Entity Framework, Hibernate, and SQLAlchemy are the most popular alternatives and competitors to Objection.js.
37
62
+ 1
0

What is Objection.js and what are its top alternatives?

It aims to stay out of your way and make it as easy as possible to use the full power of SQL and the underlying database engine while still making the common stuff easy and enjoyable.
Objection.js is a tool in the Object Relational Mapper (ORM) category of a tech stack.
Objection.js is an open source tool with 6.9K GitHub stars and 647 GitHub forks. Here’s a link to Objection.js's open source repository on GitHub

Top Alternatives to Objection.js

  • Sequelize
    Sequelize

    Sequelize is a promise-based ORM for Node.js and io.js. It supports the dialects PostgreSQL, MySQL, MariaDB, SQLite and MSSQL and features solid transaction support, relations, read replication and more. ...

  • TypeORM
    TypeORM

    It supports both Active Record and Data Mapper patterns, unlike all other JavaScript ORMs currently in existence, which means you can write high quality, loosely coupled, scalable, maintainable applications the most productive way. ...

  • Entity Framework
    Entity Framework

    It is an object-relational mapper that enables .NET developers to work with relational data using domain-specific objects. It eliminates the need for most of the data-access code that developers usually need to write. ...

  • Hibernate
    Hibernate

    Hibernate is a suite of open source projects around domain models. The flagship project is Hibernate ORM, the Object Relational Mapper. ...

  • SQLAlchemy
    SQLAlchemy

    SQLAlchemy is the Python SQL toolkit and Object Relational Mapper that gives application developers the full power and flexibility of SQL. ...

  • Dapper
    Dapper

    It is an object-relational mapping product for the Microsoft.NET platform: it provides a framework for mapping an object-oriented domain model to a traditional relational database. ...

  • Entity Framework Core
    Entity Framework Core

    It is a lightweight, extensible, open source and cross-platform version of the popular Entity Framework data access technology. It can serve as an object-relational mapper (O/RM), enabling .NET developers to work with a database using .NET objects, and eliminating the need for most of the data-access code they usually need to write. ...

  • Doctrine 2
    Doctrine 2

    Doctrine 2 sits on top of a powerful database abstraction layer (DBAL). One of its key features is the option to write database queries in a proprietary object oriented SQL dialect called Doctrine Query Language (DQL), inspired by Hibernates HQL. ...

Objection.js alternatives & related posts

Sequelize logo

Sequelize

777
1.3K
129
Easy-to-use multi SQL dialect ORM for Node.js
777
1.3K
+ 1
129
PROS OF SEQUELIZE
  • 39
    Good ORM for node.js
  • 28
    Easy setup
  • 18
    Support MySQL & MariaDB, PostgreSQL, MSSQL, Sqlite
  • 13
    Open source
  • 12
    Free
  • 11
    Promise Based
  • 4
    Recommend for mongoose users
  • 2
    Typescript
  • 2
    Atrocious documentation, buggy, issues closed by bots
CONS OF SEQUELIZE
  • 29
    Docs are awful
  • 9
    Relations can be confusing

related Sequelize posts

Dieudonné ALLOGNON
Junior Fullstack Developer · | 5 upvotes · 179K views

Hey! I am actually in internship and have an app to create for my structure. It will be an intern app which will allow crud dashboard actions with some data provided by the use of an API of one of the structure partner and make a correspondence to data contained in a private database. Since it's an intern app, I thought about Electron for a desktop app because I did a lot of web with Laravel and the structure goes more for the desktop app. But it will be my first occasion working with this tech.

Is Electron a good choice? Wich ORM should be more complete and adapted to this between Sequelize and TypeORM? (Database will be MySQL) Some charts will be displayed in the app. Is there a library (preferably without jQuery) that suits this stack?

Thank you !

See more

What is the best way to increase your income as a freelancer in 2019? What frameworks should be the best to learn? React Node.js Docker Kubernetes Sequelize Mongoose MongoDB ExpressJS hapi Based on trends I've picked up a JS full stack. If you need to work under startups you may replace React with Vue.js . If you want to work in outsourcing Angular 2+ may be better.

What is your opinion?

See more
TypeORM logo

TypeORM

552
730
72
An ORM that can run in NodeJS and others
552
730
+ 1
72
PROS OF TYPEORM
  • 28
    Typescript
  • 10
    Supports MySQL, PostgreSQL, MariaDB, SQLite, MS SQL Ser
  • 9
    Easy setup
  • 7
    Works in NodeJS, Browser, Ionic, Cordova and Electron p
  • 6
    Support MySQL & MariaDB, PostgreSQL, MSSQL, Sqlite
  • 6
    Promise Based
  • 5
    Cons of TypeORM
  • 1
    Support MongoDB
CONS OF TYPEORM
  • 5
    Completely abandoned by its creator
  • 3
    Too complex for what it does
  • 2
    Doesn't really support native javascript
  • 1
    Cannot use query on any relation
  • 1
    Not proper/real type safety

related TypeORM posts

Simon Reymann
Senior Fullstack Developer at QUANTUSflow Software GmbH · | 26 upvotes · 3.3M views

Our whole Node.js backend stack consists of the following tools:

  • Lerna as a tool for multi package and multi repository management
  • npm as package manager
  • NestJS as Node.js framework
  • TypeScript as programming language
  • ExpressJS as web server
  • Swagger UI for visualizing and interacting with the API’s resources
  • Postman as a tool for API development
  • TypeORM as object relational mapping layer
  • JSON Web Token for access token management

The main reason we have chosen Node.js over PHP is related to the following artifacts:

  • Made for the web and widely in use: Node.js is a software platform for developing server-side network services. Well-known projects that rely on Node.js include the blogging software Ghost, the project management tool Trello and the operating system WebOS. Node.js requires the JavaScript runtime environment V8, which was specially developed by Google for the popular Chrome browser. This guarantees a very resource-saving architecture, which qualifies Node.js especially for the operation of a web server. Ryan Dahl, the developer of Node.js, released the first stable version on May 27, 2009. He developed Node.js out of dissatisfaction with the possibilities that JavaScript offered at the time. The basic functionality of Node.js has been mapped with JavaScript since the first version, which can be expanded with a large number of different modules. The current package managers (npm or Yarn) for Node.js know more than 1,000,000 of these modules.
  • Fast server-side solutions: Node.js adopts the JavaScript "event-loop" to create non-blocking I/O applications that conveniently serve simultaneous events. With the standard available asynchronous processing within JavaScript/TypeScript, highly scalable, server-side solutions can be realized. The efficient use of the CPU and the RAM is maximized and more simultaneous requests can be processed than with conventional multi-thread servers.
  • A language along the entire stack: Widely used frameworks such as React or AngularJS or Vue.js, which we prefer, are written in JavaScript/TypeScript. If Node.js is now used on the server side, you can use all the advantages of a uniform script language throughout the entire application development. The same language in the back- and frontend simplifies the maintenance of the application and also the coordination within the development team.
  • Flexibility: Node.js sets very few strict dependencies, rules and guidelines and thus grants a high degree of flexibility in application development. There are no strict conventions so that the appropriate architecture, design structures, modules and features can be freely selected for the development.
See more
Martin Johannesson
Senior Software Developer at IT Minds · | 14 upvotes · 600.9K views

At IT Minds we create customized internal or #B2B web and mobile apps. I have a go to stack that I pitch to our customers consisting of 3 core areas. 1) A data core #backend . 2) A micro #serverless #backend. 3) A user client #frontend.

For the Data Core I create a backend using TypeScript Node.js and with TypeORM connecting to a PostgreSQL Exposing an action based api with Apollo GraphQL

For the micro serverless backend, which purpose is verification for authentication, autorization, logins and the likes. It is created with Next.js api pages. Using MongoDB to store essential information, caching etc.

Finally the frontend is built with React using Next.js , TypeScript and @Apollo. We create the frontend as a PWA and have a AMP landing page by default.

See more
Entity Framework logo

Entity Framework

1.5K
194
17
An object-relational mapper that enables .NET developers to work with relational data
1.5K
194
+ 1
17
PROS OF ENTITY FRAMEWORK
  • 4
    LINQ
  • 3
    Strongly Object-Oriented
  • 3
    Object Oriented
  • 2
    Code first approach
  • 2
    Multiple approach (Model/Database/Code) first
  • 1
    Model first approach
  • 1
    Auto generated code
  • 1
    Strongly typed entities
  • 0
    Database first
CONS OF ENTITY FRAMEWORK
    Be the first to leave a con

    related Entity Framework posts

    Hibernate logo

    Hibernate

    1.5K
    1.1K
    28
    Idiomatic persistence for Java and relational databases.
    1.5K
    1.1K
    + 1
    28
    PROS OF HIBERNATE
    • 19
      Easy ORM
    • 7
      Easy transaction definition
    • 2
      Is integrated with spring jpa
    CONS OF HIBERNATE
    • 3
      Can't control proxy associations when entity graph used

    related Hibernate posts

    SQLAlchemy logo

    SQLAlchemy

    864
    453
    6
    The Python SQL Toolkit and Object Relational Mapper
    864
    453
    + 1
    6
    PROS OF SQLALCHEMY
    • 6
      Open Source
    CONS OF SQLALCHEMY
    • 1
      Documentation

    related SQLAlchemy posts

    Django Stars
    Developer at Django Stars · | 3 upvotes · 124.8K views

    Merging Django ORM with SQLAlchemy for Easier Data Analysis (Video Inside)

    Development of products with Django framework is usually easy and straightforward; great documentation, many tools out of the box, plenty of open source libraries and big community. Django ORM takes full control about SQL layer protecting you from mistakes, and underlying details of queries so you can spend more time on designing and building your application structure in Python code. However, sometimes such behavior may hurt - for example, when you’re building a project related to data analysis. Building advanced queries with Django is not very easy; it’s hard to read (in Python) and hard to understand what’s going on in SQL-level without logging or printing generated SQL queries somewhere. Moreover, such queries could not be efficient enough, so this will hit you back when you load more data into DB to play with. In one moment, you can find yourself doing too much raw SQL through Django cursor, and this is the moment when you should do a break and take a look on another interesting tool, which is placed right between ORM layer and the layer of raw SQL queries.

    See more
    Dapper logo

    Dapper

    532
    65
    6
    A simple object mapper for .Net
    532
    65
    + 1
    6
    PROS OF DAPPER
    • 6
      Fastest ORM
    CONS OF DAPPER
      Be the first to leave a con

      related Dapper posts

      Entity Framework Core logo

      Entity Framework Core

      272
      203
      16
      Lightweight and cross-platform version of the popular Entity Framework
      272
      203
      + 1
      16
      PROS OF ENTITY FRAMEWORK CORE
      • 7
        Fits very well with Microsoft technologies
      • 4
        Fast
      • 2
        Linq
      • 1
        OpenSource
      • 1
        Multiple Database provider
      • 1
        Easy to use
      CONS OF ENTITY FRAMEWORK CORE
      • 1
        Dbcontext

      related Entity Framework Core posts

      Doctrine 2 logo

      Doctrine 2

      270
      202
      31
      An object-relational mapper (ORM) for PHP 5.3.2+ that provides transparent persistence for PHP objects
      270
      202
      + 1
      31
      PROS OF DOCTRINE 2
      • 14
        Great abstraction, easy to use, good docs
      • 10
        Object-Oriented
      • 7
        Easy setup
      CONS OF DOCTRINE 2
        Be the first to leave a con

        related Doctrine 2 posts