Need advice about which tool to choose?Ask the StackShare community!
Sails.js vs TypeORM: What are the differences?
Developers describe Sails.js as "Realtime MVC Framework for Node.js". Sails is designed to mimic the MVC pattern of frameworks like Ruby on Rails, but with support for the requirements of modern apps: data-driven APIs with scalable, service-oriented architecture. On the other hand, TypeORM is detailed as "An ORM that can run in NodeJS and others". 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.
Sails.js and TypeORM belong to "Microframeworks (Backend)" category of the tech stack.
Sails.js and TypeORM are both open source tools. It seems that Sails.js with 20.7K GitHub stars and 1.85K forks on GitHub has more adoption than TypeORM with 14.4K GitHub stars and 1.85K GitHub forks.
According to the StackShare community, Sails.js has a broader approval, being mentioned in 47 company stacks & 150 developers stacks; compared to TypeORM, which is listed in 9 company stacks and 22 developer stacks.
Pros of Sails.js
- Data-driven apis49
- Waterline ORM47
- Mvc37
- Easy rest32
- Real-time25
- Open source21
- Service-oriented architecture19
- Scalable18
- Convension over configuration10
- Rails-like asset pipeline9
- Node machines and machinepacks9
- Easy route/controller generation7
- Ruby on Rails basic stuff for JS devs6
- CLI for scaffolding project pieces3
- WebSocket support3
- Supportive community1
Pros of TypeORM
- Typescript28
- Supports MySQL, PostgreSQL, MariaDB, SQLite, MS SQL Ser10
- Easy setup9
- Works in NodeJS, Browser, Ionic, Cordova and Electron p7
- Support MySQL & MariaDB, PostgreSQL, MSSQL, Sqlite6
- Promise Based6
- Cons of TypeORM5
- Support MongoDB1
Sign up to add or upvote prosMake informed product decisions
Cons of Sails.js
- Waterline ORM5
- Defaults to VueJS4
- Standard MVC0
Cons of TypeORM
- Completely abandoned by its creator5
- Too complex for what it does3
- Doesn't really support native javascript2
- Cannot use query on any relation1
- Not proper/real type safety1