Alternatives to Sequelize logo

Alternatives to Sequelize

Marvel, Sequel, TypeORM, Mongoose, and Prisma are the most popular alternatives and competitors to Sequelize.
858
1.4K
+ 1
142

What is Sequelize and what are its top alternatives?

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.
Sequelize is a tool in the Object Relational Mapper (ORM) category of a tech stack.
Sequelize is an open source tool with 29K GitHub stars and 4.2K GitHub forks. Here’s a link to Sequelize's open source repository on GitHub

Top Alternatives to Sequelize

  • Marvel
    Marvel

    A super simple tool that turns any image (including PSDs) or sketch into interactive prototypes for any device. Powered by Dropbox. ...

  • Sequel
    Sequel

    It is a simple, flexible, and powerful SQL database access toolkit for Ruby. It includes a comprehensive ORM layer for mapping records to Ruby objects and handling associated records. ...

  • 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. ...

  • Mongoose
    Mongoose

    Let's face it, writing MongoDB validation, casting and business logic boilerplate is a drag. That's why we wrote Mongoose. Mongoose provides a straight-forward, schema-based solution to modeling your application data and includes built-in type casting, validation, query building, business logic hooks and more, out of the box. ...

  • Prisma
    Prisma

    Prisma is an open-source database toolkit. It replaces traditional ORMs and makes database access easy with an auto-generated query builder for TypeScript & Node.js. ...

  • 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. ...

  • 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. ...

Sequelize alternatives & related posts

Marvel logo

Marvel

187
180
46
Prototyping for everyone
187
180
+ 1
46
PROS OF MARVEL
  • 15
    Nice UI
  • 14
    Free
  • 7
    Easy animations
  • 5
    Iphone app
  • 5
    Dropbox integration
CONS OF MARVEL
    Be the first to leave a con

    related Marvel posts

    Sequel logo

    Sequel

    22
    21
    0
    The database toolkit for Ruby
    22
    21
    + 1
    0
    PROS OF SEQUEL
      Be the first to leave a pro
      CONS OF SEQUEL
        Be the first to leave a con

        related Sequel posts

        TypeORM logo

        TypeORM

        566
        802
        78
        An ORM that can run in NodeJS and others
        566
        802
        + 1
        78
        PROS OF TYPEORM
        • 29
          Typescript
        • 11
          Supports MySQL, PostgreSQL, MariaDB, SQLite, MS SQL Ser
        • 9
          Easy setup
        • 8
          Cons of TypeORM
        • 7
          Promise Based
        • 7
          Works in NodeJS, Browser, Ionic, Cordova and Electron p
        • 6
          Support MySQL & MariaDB, PostgreSQL, MSSQL, Sqlite
        • 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
          Not proper/real type safety
        • 1
          Cannot use query on any relation

        related TypeORM posts

        Simon Reymann
        Senior Fullstack Developer at QUANTUSflow Software GmbH · | 27 upvotes · 4.7M 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 · 2.8M 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
        Mongoose logo

        Mongoose

        2K
        1.3K
        56
        MongoDB object modeling designed to work in an asynchronous environment
        2K
        1.3K
        + 1
        56
        PROS OF MONGOOSE
        • 17
          Several bad ideas mixed together
        • 17
          Well documented
        • 10
          JSON
        • 8
          Actually terrible documentation
        • 2
          Recommended and used by Valve. See steamworks docs
        • 1
          Can be used with passportjs for oauth
        • 1
          Yeah
        CONS OF MONGOOSE
        • 3
          Model middleware/hooks are not user friendly

        related Mongoose posts

        Repost

        Overview: To put it simply, we plan to use the MERN stack to build our web application. MongoDB will be used as our primary database. We will use ExpressJS alongside Node.js to set up our API endpoints. Additionally, we plan to use React to build our SPA on the client side and use Redis on the server side as our primary caching solution. Initially, while working on the project, we plan to deploy our server and client both on Heroku . However, Heroku is very limited and we will need the benefits of an Infrastructure as a Service so we will use Amazon EC2 to later deploy our final version of the application.

        Serverside: nodemon will allow us to automatically restart a running instance of our node app when files changes take place. We decided to use MongoDB because it is a non relational database which uses the Document Object Model. This allows a lot of flexibility as compared to a RDMS like SQL which requires a very structural model of data that does not change too much. Another strength of MongoDB is its ease in scalability. We will use Mongoose along side MongoDB to model our application data. Additionally, we will host our MongoDB cluster remotely on MongoDB Atlas. Bcrypt will be used to encrypt user passwords that will be stored in the DB. This is to avoid the risks of storing plain text passwords. Moreover, we will use Cloudinary to store images uploaded by the user. We will also use the Twilio SendGrid API to enable automated emails sent by our application. To protect private API endpoints, we will use JSON Web Token and Passport. Also, PayPal will be used as a payment gateway to accept payments from users.

        Client Side: As mentioned earlier, we will use React to build our SPA. React uses a virtual DOM which is very efficient in rendering a page. Also React will allow us to reuse components. Furthermore, it is very popular and there is a large community that uses React so it can be helpful if we run into issues. We also plan to make a cross platform mobile application later and using React will allow us to reuse a lot of our code with React Native. Redux will be used to manage state. Redux works great with React and will help us manage a global state in the app and avoid the complications of each component having its own state. Additionally, we will use Bootstrap components and custom CSS to style our app.

        Other: Git will be used for version control. During the later stages of our project, we will use Google Analytics to collect useful data regarding user interactions. Moreover, Slack will be our primary communication tool. Also, we will use Visual Studio Code as our primary code editor because it is very light weight and has a wide variety of extensions that will boost productivity. Postman will be used to interact with and debug our API endpoints.

        See more

        Overview: To put it simply, we plan to use the MERN stack to build our web application. MongoDB will be used as our primary database. We will use ExpressJS alongside Node.js to set up our API endpoints. Additionally, we plan to use React to build our SPA on the client side and use Redis on the server side as our primary caching solution. Initially, while working on the project, we plan to deploy our server and client both on Heroku. However, Heroku is very limited and we will need the benefits of an Infrastructure as a Service so we will use Amazon EC2 to later deploy our final version of the application.

        Serverside: nodemon will allow us to automatically restart a running instance of our node app when files changes take place. We decided to use MongoDB because it is a non relational database which uses the Document Object Model. This allows a lot of flexibility as compared to a RDMS like SQL which requires a very structural model of data that does not change too much. Another strength of MongoDB is its ease in scalability. We will use Mongoose along side MongoDB to model our application data. Additionally, we will host our MongoDB cluster remotely on MongoDB Atlas. Bcrypt will be used to encrypt user passwords that will be stored in the DB. This is to avoid the risks of storing plain text passwords. Moreover, we will use Cloudinary to store images uploaded by the user. We will also use the Twilio SendGrid API to enable automated emails sent by our application. To protect private API endpoints, we will use JSON Web Token and Passport. Also, PayPal will be used as a payment gateway to accept payments from users.

        Client Side: As mentioned earlier, we will use React to build our SPA. React uses a virtual DOM which is very efficient in rendering a page. Also React will allow us to reuse components. Furthermore, it is very popular and there is a large community that uses React so it can be helpful if we run into issues. We also plan to make a cross platform mobile application later and using React will allow us to reuse a lot of our code with React Native. Redux will be used to manage state. Redux works great with React and will help us manage a global state in the app and avoid the complications of each component having its own state. Additionally, we will use Bootstrap components and custom CSS to style our app.

        Other: Git will be used for version control. During the later stages of our project, we will use Google Analytics to collect useful data regarding user interactions. Moreover, Slack will be our primary communication tool. Also, we will use Visual Studio Code as our primary code editor because it is very light weight and has a wide variety of extensions that will boost productivity. Postman will be used to interact with and debug our API endpoints.

        See more
        Prisma logo

        Prisma

        1K
        927
        54
        Modern Database Access for TypeScript & Node.js
        1K
        927
        + 1
        54
        PROS OF PRISMA
        • 12
          Type-safe database access
        • 10
          Open Source
        • 8
          Auto-generated query builder
        • 6
          Supports multible database systems
        • 6
          Increases confidence during development
        • 4
          Built specifically for Postgres and TypeScript
        • 4
          Productive application development
        • 2
          Supports multible RDBMSs
        • 2
          Robust migrations system
        CONS OF PRISMA
        • 2
          Doesn't support downward/back migrations
        • 1
          Doesn't support JSONB
        • 1
          Do not support JSONB
        • 1
          Mutation of JSON is really confusing
        • 1
          Do not support JSONB

        related Prisma posts

        Divine Bawa
        at PayHub Ghana Limited · | 16 upvotes · 482.9K views

        I just finished a web app meant for a business that offers training programs for certain professional courses. I chose this stack to test out my skills in graphql and react. I used Node.js , GraphQL , MySQL for the #Backend utilizing Prisma as a database interface for MySQL to provide CRUD APIs and graphql-yoga as a server. For the #frontend I chose React, styled-components for styling, Next.js for routing and SSR and Apollo for data management. I really liked the outcome and I will definitely use this stack in future projects.

        See more
        Collins Ogbuzuru
        Front-end dev at Evolve credit · | 11 upvotes · 25.4K views
        Shared insights
        on
        GraphQLGraphQLPrismaPrismaAWS LambdaAWS Lambda

        We are starting to build one shirt data logic, structure and as an online clothing store we believe good ux and ui is a goal to drive a lot of click through. The problem is, how do we fetch data and how do we abstract the gap between the Front-end devs and backend-devs as we are just two in the technical unit. We decided to go for GraphQL as our application-layer tool and Prisma for our database-layer abstracter.

        Reasons :

        GraphQL :

        1. GraphQL makes fetching of data less painful and organised.

        2. GraphQL gives you 100% assurance on data you getting back as opposed to the Rest design .

        3. GraphQL comes with a bunch of real-time functionality in form of. subscriptions and finally because we are using React (GraphQL is not React demanding, it's doesn't require a specific framework, language or tool, but it definitely makes react apps fly )

        Prisma :

        1. Writing revolvers can be fun, but imagine writing revolvers nested deep down, curry braces flying around. This is sure a welcome note to bugs and as a small team we need to focus more on what that matters more. Prisma generates this necessary CRUD resolves, mutations and subscription out of the box.

        2. We don't really have much budget at the moment so we are going to run our logic in a scalable cheap and cost effective cloud environment. Oh! It's AWS Lambda and deploying our schema to Lambda is our best bet to minimize cost and same time scale.

        We are still at development stage and I believe, working on this start up will increase my dev knowledge. Off for Lunch :)

        See more
        Hibernate logo

        Hibernate

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

        related Hibernate posts

        SQLAlchemy logo

        SQLAlchemy

        936
        498
        7
        The Python SQL Toolkit and Object Relational Mapper
        936
        498
        + 1
        7
        PROS OF SQLALCHEMY
        • 7
          Open Source
        CONS OF SQLALCHEMY
        • 2
          Documentation

        related SQLAlchemy posts

        Hello everybody! I want to create an easy to use website (and simplified) builder. Users create a site, add their domain and edit Pages inside an Admin Area inside predefined "Blocks" like with Wagtail.

        There should be several default templates/themes and layouts. Choosing a different theme might change both the layout and styling. And I'm looking for SSR or SSG with a focus on the end-user's Page performance.

        Current Stack:

        • GraphQL for the dynamic part (for example data to Pricing might not be required on the homepage, or images might go into gallery in one theme, and on the homepage in another theme)

        • FastAPI and SQLAlchemy to store Data. I have prior experience with Wagtail and Django and want to stay with Python and learn Fastapi

        • NGINX to handle domain-specific things (the how is not yet refined)

        I want a scalable architecture and especially a fast frontend. I'm tending to use SvelteKit, but I'm afraid that the dynamic part won't make me happy after having hundreds of sites, as the bundler cannot load themes dynamically. sveltekit - dynamic import

        I want to handle the scenario: Admin-User chooses a theme and other options for the site (domain) and the End-User Frontend/Session/Cookie will have to fetch and store data about the theme and load subsequent calls to prerendered sites.

        Also the "hundreds of sites" might not be all covered by 5 Themes, because users may purchase a custom-made theme, and I would have to manage one big project having lots of different Styleguides and flows. I even thought of statically building the site whenever the user makes a change, maybe using Hugo (or VitePress?). Then I would have to take more care with the page recreation and it would be easily routable instead of nesting every component with logic in the frontend... I think. But this I haven't thought through yet.

        Can anyone please help?

        See more
        Django Stars
        Developer at Django Stars · | 3 upvotes · 223.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
        Entity Framework logo

        Entity Framework

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

          related Entity Framework posts