StackShareStackShare
Follow on
StackShare

Discover and share technology stacks from companies around the world.

Follow on

© 2025 StackShare. All rights reserved.

Product

  • Stacks
  • Tools
  • Feed

Company

  • About
  • Contact

Legal

  • Privacy Policy
  • Terms of Service
  1. Stackups
  2. Application & Data
  3. Frameworks
  4. Frameworks
  5. Django REST framework vs Rails

Django REST framework vs Rails

OverviewDecisionsComparisonAlternatives

Overview

Rails
Rails
Stacks20.2K
Followers13.8K
Votes5.5K
GitHub Stars57.8K
Forks22.0K
Django REST framework
Django REST framework
Stacks1.9K
Followers2.1K
Votes312

Django REST framework vs Rails: What are the differences?

Django REST framework: Web APIs for Django. Django REST framework is a powerful and flexible toolkit that makes it easy to build Web APIs; Rails: 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.

Django REST framework can be classified as a tool in the "Microframeworks (Backend)" category, while Rails is grouped under "Frameworks (Full Stack)".

"Browsable api" is the primary reason why developers consider Django REST framework over the competitors, whereas "Rapid development" was stated as the key factor in picking Rails.

Django REST framework and Rails are both open source tools. Rails with 43.6K GitHub stars and 17.5K forks on GitHub appears to be more popular than Django REST framework with 14.7K GitHub stars and 4.33K GitHub forks.

According to the StackShare community, Rails has a broader approval, being mentioned in 2321 company stacks & 797 developers stacks; compared to Django REST framework, which is listed in 159 company stacks and 79 developer stacks.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs
CLI (Node.js)
or
Manual

Advice on Rails, Django REST framework

Shivam
Shivam

AVP - Business at VAYUZ Technologies Pvt. Ltd.

Mar 25, 2020

Needs adviceonNode.jsNode.jsJavaJavaRailsRails

Hi Community! Trust everyone is keeping safe. I am exploring the idea of building a #Neobank (App) with end-to-end banking capabilities. In the process of exploring this space, I have come across multiple Apps (N26, Revolut, Monese, etc) and explored their stacks in detail. The confusion remains to be the Backend Tech to be used?

What would you go with considering all of the languages such as Node.js Java Rails Python are suggested by some person or the other. As a general trend, I have noticed the usage of Node with React on the front or Node with a combination of Kotlin and Swift. Please suggest what would be the right approach!

915k views915k
Comments
Ben
Ben

May 19, 2020

Decided

As a small team, we wanted to pick the framework which allowed us to move quickly. There's no option better than Rails. Not having to solve the fundamentals means we can more quickly build our feature set. No other framework can beat ActiveRecord in terms of integration & ease-of use. To top it all of, there's a lot of attention paid to security in the framework, making almost everything safe-by-default.

482k views482k
Comments
Felipe
Felipe

May 24, 2020

Decided

Since I came from python I had two choices: #django or #flask. It felt like it was a better idea to go for #django considering I was building a blogging platform, this is kind of what #django was made for. On the other hand, #rails seems to be a fantastic framework to get things done. Although I do not regret any of my time spent on developing with #django I want to give @{#rails}|topic:null| a try some day in the future for the sake of curiosity.

438k views438k
Comments

Detailed Comparison

Rails
Rails
Django REST framework
Django REST framework

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

It is a powerful and flexible toolkit that makes it easy to build Web APIs.

-
The Web browsable API is a huge usability win for your developers.;Authentication policies including OAuth1a and OAuth2 out of the box.;Serialization that supports both ORM and non-ORM data sources.;Customizable all the way down - just use regular function-based views if you don't need the more powerful features.;Extensive documentation, and great community support.;Used and trusted by large companies such as Mozilla and Eventbrite.
Statistics
GitHub Stars
57.8K
GitHub Stars
-
GitHub Forks
22.0K
GitHub Forks
-
Stacks
20.2K
Stacks
1.9K
Followers
13.8K
Followers
2.1K
Votes
5.5K
Votes
312
Pros & Cons
Pros
  • 860
    Rapid development
  • 653
    Great gems
  • 607
    Great community
  • 486
    Convention over configuration
  • 418
    Mvc
Cons
  • 24
    Too much "magic" (hidden behavior)
  • 14
    Poor raw performance
  • 12
    Asset system is too primitive and outdated
  • 6
    Bloat in models
  • 6
    Heavy use of mixins
Pros
  • 67
    Easy to use
  • 65
    Browsable api
  • 53
    Great documentation
  • 51
    Customizable
  • 42
    Fast development
Cons
  • 2
    Bad documentation
  • 2
    Reimplements Django functionality
  • 1
    No support for URL Namespaces
  • 0
    Bad CSRF handling
Integrations
Ruby
Ruby
Rollbar
Rollbar
Sentry
Sentry
Django
Django
Stream
Stream
Kloudless
Kloudless

What are some alternatives to Rails, Django REST framework?

Node.js

Node.js

Node.js uses an event-driven, non-blocking I/O model that makes it lightweight and efficient, perfect for data-intensive real-time applications that run across distributed devices.

Django

Django

Django is a high-level Python Web framework that encourages rapid development and clean, pragmatic design.

Laravel

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.

.NET

.NET

.NET is a general purpose development platform. With .NET, you can use multiple languages, editors, and libraries to build native applications for web, mobile, desktop, gaming, and IoT for Windows, macOS, Linux, Android, and more.

ASP.NET Core

ASP.NET Core

A free and open-source web framework, and higher performance than ASP.NET, developed by Microsoft and the community. It is a modular framework that runs on both the full .NET Framework, on Windows, and the cross-platform .NET Core.

ExpressJS

ExpressJS

Express is a minimal and flexible node.js web application framework, providing a robust set of features for building single and multi-page, and hybrid web applications.

Symfony

Symfony

It is written with speed and flexibility in mind. It allows developers to build better and easy to maintain websites with PHP..

Spring

Spring

A key element of Spring is infrastructural support at the application level: Spring focuses on the "plumbing" of enterprise applications so that teams can focus on application-level business logic, without unnecessary ties to specific deployment environments.

Spring Boot

Spring Boot

Spring Boot makes it easy to create stand-alone, production-grade Spring based Applications that you can "just run". We take an opinionated view of the Spring platform and third-party libraries so you can get started with minimum fuss. Most Spring Boot applications need very little Spring configuration.

Android SDK

Android SDK

Android provides a rich application framework that allows you to build innovative apps and games for mobile devices in a Java language environment.

Related Comparisons

Bootstrap
Materialize

Bootstrap vs Materialize

Laravel
Django

Django vs Laravel vs Node.js

Bootstrap
Foundation

Bootstrap vs Foundation vs Material UI

Node.js
Spring Boot

Node.js vs Spring-Boot

Liquibase
Flyway

Flyway vs Liquibase