Need advice about which tool to choose?Ask the StackShare community!
Rails API vs Sails.js: What are the differences?
Rails API: Rails for API only applications. Rails::API is a subset of a normal Rails application, created for applications that don't require all functionality that a complete Rails application provides. It is a bit more lightweight, and consequently a bit faster than a normal Rails application. The main example for its usage is in API applications only, where you usually don't need the entire Rails middleware stack nor template generation; Sails.js: 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.
Rails API and Sails.js can be categorized as "Microframeworks (Backend)" tools.
"Great for quick decoupled apps" is the top reason why over 4 developers like Rails API, while over 41 developers mention "Data-driven apis " as the leading cause for choosing Sails.js.
Rails API and Sails.js are both open source tools. Sails.js with 20.6K GitHub stars and 1.85K forks on GitHub appears to be more popular than Rails API with 5.27K GitHub stars and 293 GitHub forks.
Pros of Rails API
- Great for quick decoupled apps5
- Lightweight5
- Simply the best3
- Soon to be merged into core Rails 52
- Logging by default1
Pros of Sails.js
- Data-driven apis46
- Waterline ORM44
- Mvc34
- Easy rest30
- Real-time22
- Open source18
- Service-oriented architecture17
- Scalable16
- Convension over configuration8
- Rails-like asset pipeline7
- Node machines and machinepacks7
- Easy route/controller generation5
- Ruby on Rails basic stuff for JS devs4
- WebSocket support1
- CLI for scaffolding project pieces1
Sign up to add or upvote prosMake informed product decisions
Cons of Rails API
Cons of Sails.js
- Waterline ORM4
- Defaults to VueJS2