Get Advice Icon

Need advice about which tool to choose?Ask the StackShare community!

Rails
Rails

8.7K
5.4K
+ 1
5.3K
Vapor
Vapor

39
57
+ 1
29
Add tool

Rails vs Vapor: What are the differences?

Developers describe Rails as "Web development that doesn't hurt". Rails is a web-application framework that includes everything needed to create database-backed web applications according to the Model-View-Controller (MVC) pattern. On the other hand, Vapor is detailed as "A type-safe web framework for Swift". Vapor is the first true web framework for Swift. It provides a beautifully expressive foundation for your app without tying you to any single server implementation.

Rails and Vapor can be primarily classified as "Frameworks (Full Stack)" tools.

"Rapid development" is the primary reason why developers consider Rails over the competitors, whereas "Fast" was stated as the key factor in picking Vapor.

Rails and Vapor are both open source tools. It seems that Rails with 43.6K GitHub stars and 17.5K forks on GitHub has more adoption than Vapor with 16.8K GitHub stars and 997 GitHub forks.

Airbnb, Twitter, and Instacart are some of the popular companies that use Rails, whereas Vapor is used by Applicodo, N26, and Nodes. Rails has a broader approval, being mentioned in 2321 company stacks & 796 developers stacks; compared to Vapor, which is listed in 6 company stacks and 5 developer stacks.

What is Rails?

Rails is a web-application framework that includes everything needed to create database-backed web applications according to the Model-View-Controller (MVC) pattern.

What is Vapor?

Vapor is the first true web framework for Swift. It provides a beautifully expressive foundation for your app without tying you to any single server implementation.
Get Advice Icon

Need advice about which tool to choose?Ask the StackShare community!

Why do developers choose Rails?
Why do developers choose Vapor?

Sign up to add, upvote and see more prosMake informed product decisions

Sign up to add, upvote and see more consMake informed product decisions

What companies use Rails?
What companies use Vapor?

Sign up to get full access to all the companiesMake informed product decisions

What tools integrate with Rails?
What tools integrate with Vapor?

Sign up to get full access to all the tool integrationsMake informed product decisions

What are some alternatives to Rails and Vapor?
Django
Django is a high-level Python Web framework that encourages rapid development and clean, pragmatic design.
Ruby
Ruby is a language of careful balance. Its creator, Yukihiro “Matz” Matsumoto, blended parts of his favorite languages (Perl, Smalltalk, Eiffel, Ada, and Lisp) to form a new language that balanced functional programming with imperative programming.
Sinatra
Sinatra is a DSL for quickly creating web applications in Ruby with minimal effort.
React
Lots of people use React as the V in MVC. Since React makes no assumptions about the rest of your technology stack, it's easy to try it out on a small feature in an existing project.
Laravel
It is a web application framework with expressive, elegant syntax. It attempts to take the pain out of development by easing common tasks used in the majority of web projects, such as authentication, routing, sessions, and caching.
See all alternatives
Decisions about Rails and Vapor
StackShare Editors
StackShare Editors
Rails
Rails
Node.js
Node.js
Python
Python
React
React
Java
Java
Ruby
Ruby
Go
Go
Swift
Swift
Objective-C
Objective-C
jQuery
jQuery

By mid-2015, around the time of the Series E, the Digital department at WeWork had grown to more than 40 people to support the company’s growing product needs.

By then, they’d migrated the main website off of WordPress to Ruby on Rails, and a combination React, Angular, and jQuery, though there were efforts to move entirely to React for the front-end.

The backend was structured around a microservices architecture built partially in Node.js, along with a combination of Ruby, Python, Bash, and Go. Swift/Objective-C and Java powered the mobile apps.

These technologies power the listings on the website, as well as various internal tools, like community manager dashboards as well as RFID hardware for access management.

See more
Spenser Coke
Spenser Coke
Product Engineer at Loanlink.de · | 8 upvotes · 151.6K views
atLoanlink GmbhLoanlink Gmbh
Rails
Rails
AngularJS
AngularJS
.NET
.NET
Node.js
Node.js
React
React
GitHub
GitHub
Trello
Trello
Zapier
Zapier
Mailchimp
Mailchimp
Google Drive
Google Drive
Vue.js
Vue.js
HTML5
HTML5

When starting a new company and building a new product w/ limited engineering we chose to optimize for expertise and rapid development, landing on Rails API, w/ AngularJS on the front.

The reality is that we're building a CRUD app, so we considered going w/ vanilla Rails MVC to optimize velocity early on (it may not be sexy, but it gets the job done). Instead, we opted to split the codebase to allow for a richer front-end experience, focus on skill specificity when hiring, and give us the flexibility to be consumed by multiple clients in the future.

We also considered .NET core or Node.js for the API layer, and React on the front-end, but our experiences dealing with mature Node APIs and the rapid-fire changes that comes with state management in React-land put us off, given our level of experience with those tools.

We're using GitHub and Trello to track issues and projects, and a plethora of other tools to help the operational team, like Zapier, MailChimp, Google Drive with some basic Vue.js & HTML5 apps for smaller internal-facing web projects.

See more
Russel Werner
Russel Werner
Lead Engineer at StackShare · | 19 upvotes · 245.2K views
atStackShareStackShare
React
React
Glamorous
Glamorous
Apollo
Apollo
Node.js
Node.js
Rails
Rails
Heroku
Heroku
GitHub
GitHub
Amazon S3
Amazon S3
Amazon CloudFront
Amazon CloudFront
Webpack
Webpack
CircleCI
CircleCI
Redis
Redis
#StackDecisionsLaunch
#SSR
#Microservices
#FrontEndRepoSplit

StackShare Feed is built entirely with React, Glamorous, and Apollo. One of our objectives with the public launch of the Feed was to enable a Server-side rendered (SSR) experience for our organic search traffic. When you visit the StackShare Feed, and you aren't logged in, you are delivered the Trending feed experience. We use an in-house Node.js rendering microservice to generate this HTML. This microservice needs to run and serve requests independent of our Rails web app. Up until recently, we had a mono-repo with our Rails and React code living happily together and all served from the same web process. In order to deploy our SSR app into a Heroku environment, we needed to split out our front-end application into a separate repo in GitHub. The driving factor in this decision was mostly due to limitations imposed by Heroku specifically with how processes can't communicate with each other. A new SSR app was created in Heroku and linked directly to the frontend repo so it stays in-sync with changes.

Related to this, we need a way to "deploy" our frontend changes to various server environments without building & releasing the entire Ruby application. We built a hybrid Amazon S3 Amazon CloudFront solution to host our Webpack bundles. A new CircleCI script builds the bundles and uploads them to S3. The final step in our rollout is to update some keys in Redis so our Rails app knows which bundles to serve. The result of these efforts were significant. Our frontend team now moves independently of our backend team, our build & release process takes only a few minutes, we are now using an edge CDN to serve JS assets, and we have pre-rendered React pages!

#StackDecisionsLaunch #SSR #Microservices #FrontEndRepoSplit

See more
Julien DeFrance
Julien DeFrance
Principal Software Engineer at Tophatter · | 16 upvotes · 505.5K views
atSmartZipSmartZip
Rails
Rails
Rails API
Rails API
AWS Elastic Beanstalk
AWS Elastic Beanstalk
Capistrano
Capistrano
Docker
Docker
Amazon S3
Amazon S3
Amazon RDS
Amazon RDS
MySQL
MySQL
Amazon RDS for Aurora
Amazon RDS for Aurora