Ruby on Rails vs Django

Compare of features and capabilities of two popular frameworks
12 July 2017   3024
Ruby on Rails

Framework written in the Ruby programming language

Comparing frameworks is a hard task. Each platform is developed to solve specific problems and has its advantages and disadvantages. Therefore, the framework, unsuitable for some projects and programmers, can perfectly prove for others.

To develop web applications, many auxiliary tools have been created in different languages. The two most popular platforms are Rails, which uses Ruby, and Django, written in Python. Let's figure out what are the differences between them and for what tasks they are intended.

Used model

Both frameworks implement development using the MVC model. As follows from the deciphering of the abbreviation, this template includes three main blocks:

  1. Model. The main project databases are: users, posts, comments and the like.
  2. Performance. Visual display of information from the model.
  3. Controller. Intermediate link between the model and the view, which processes the requests of users and demonstrates the result of their actions.

There is no significant difference in the representation of these blocks in the frameworks. In Django, some templates are called differently, but they use same principles as Rails do.

Accessibility for beginners

Python's code is easy to read. It does not use complex syntax. Incomprehensible abbreviations, punctuation marks and special characters almost never occur. A beginner Django-developer will be able to write own and understand colleagues code.

Studying Rails is a bit longer proccess. It also doesn't have complicated syntax, but without learning it is hard to understand the code. However, having mastered the language, in the future it will be easier and more pleasant to work with: it is more flexible than Python, and Rails offers more useful tools for creating web applications than Django.



High-level, free and open source Python Web framework.

Django fully realizes the concept of Python, which is primarily based on the simplicity of the syntax and the ability to write quality code quickly. However, the framework itself requires a good knowledge of its internal structure and available capabilities: for determining the MVC and URL routes, you will need to use regular expressions, and all classes and variables must be explicitly written.

Ruby on Rails offers more ready-made solutions. A lot of actions are automated, for example, inheritance of methods. The same goes for definitions - there is no need to add classes and variables manually, the framework will do it yourself. On the other hand, this approach alleviates the life of the programmer, but does not make it clear how the application is built in detail.


Frameworks are created on the basis of scripting interpreted languages, so there is no big difference in speed. However, Ruby is still slower than Python, which affects the work of Rails. However, it will be noticeable only in high-loaded projects. The rest, most likely, will not feel the difference.

Availability of libraries

Perhaps the only parameter by which Ruby on Rails is unconditionally better than Django - there are more plugins and extensions for this framework than for Python. But this does not mean that Django will have to work without libraries at all. They exist, and there are many of them. However, RoR is still able to provide more.

Support for language and community developers

Django documentation is more detailed and completed, it is easy to find the answer to any question that arises. Rails has a less detailed and slightly worse structured help system. However, this does not greatly complicate the work with the language - you can not call the RoR documentation incomplete.

Both Python and Rails has a large, fully-formed community. However, it is not the same. An important difference of the Django community is its multi-profile. The framework does not have well-defined boundaries of application and can be used to create any applications. Ruby on Rails is designed for web development, so there are very few discussions in its community related to solving other problems.

Final comparison of Ruby on Rails and Django

Django Ruby on Rails
Simple syntax More complicated syntax
High performance Lower performance
Mandatory class and variable definitions Automatic definition of classes and variables without explicit definition
Creating MVC and URL Routines with Regular Expressions Automatic creation of MVC and URL routes
Small number of libraries Significant selection of extensions
Detailed documentartion Less detailed documentation
Suitable for creating any applications Suitable for web development

What framework do you like more?

In your opinion, what technology is the most interesting and has bigger future? Django is Python based framework with high performance but small nimber of availabe libraries and Rails are the Ruby framework with lower performance but with bigger selection of extensions.

Ruby on Rails
64% (27 votes)
36% (15 votes)
Total votes: 42

Charles Nutter. How to move your Ruby project to JRuby and why

Charles Nutter works on JRuby and JVM language support at Red Hat.
03 October 2018   953

— How did you get into programming and into Ruby world?

— In 2004, I was working at a government contracting firm as a Java Enterprise Architect. I was in charge of a large mainframe conversion for the United States Department of Agriculture, which meant I spent a couple weeks a month in the Washington D.C. area. One of those trips coincided with RubyConf 2004, and since a close friend had been recommending I look at Ruby, I decided to attend. So there I was sitting in a Ruby conference without ever having learned Ruby...and I understood every piece of code, every example. I was amazed and vowed to find a way to bring Ruby into my Java world.

— Which projects are you working on now?

— My primary role is as co-lead of JRuby. This also means supporting several side projects like our native-library backend (Ruby's FFI library is maintained by us using this backend on JRuby) and our String encoding subsystem (an elaborate port of the logic from CRuby). I also do much of the outreach to the community and try to make sure our users are getting their issues addressed. There's always plenty to work on!

— Which one would have the biggest general impact from you opinion?

— I like to think that JRuby, while not the most popular JVM language, has at least helped to change the JVM platform. Because of our collaborations with Sun Microsystems, Oracle, and others, we have solid dynamic language support at the JVM level along with many other projects to support alternative languages. The JVM today is a much more hospitable home for non-Java languages than it used to be, and I hope we've played some small part in that change.

— Which languages are you writing on in your everyday life? Which one do you like most? Why?

— Most days I write in a mix of Ruby and Java, since JRuby is implemented using both. I like both languages for different tasks. Ruby is a better language for building applications that need to evolve and adapt quickly. Java is a great language for writing high-speed, reliable libraries and services. JRuby gives you the best of both worlds!

— Do you like to program in Java?

— I do, especially with all the language improvements that have been added recently, like lambdas (closures or blocks in Ruby) and the new "var" syntax for declaring local variables when the static type is unambiguous.

— What do you think about Rust?

— Rust is a great language! I did a lot of C++ development in my college years, and I can tell you right now if I'd had Rust available then I would have used it. I'm especially jealous of the static-typed ownership model, which helps avoid thread-safety issues like races and data corruption. I hope to see other languages adopt this pattern in the future.

— What do you think about the Ruby language perspective? Is it or its community dying?

— After all these years working on JRuby, I do still love Ruby syntax and the Ruby way of doing things. However I worry that the language is held back too much by limitations of its primary runtime. JRuby has been fighting to make true parallel threading a reality for Ruby developers, but still today the vast majority of Ruby services are run using multiple isolated processes, wasting tremendous amounts of CPU and memory resources. I believe this is due to the C API for writing Ruby extensions being so large and so prevents many improvements -- including parallel threading -- from being developed. Hopefully we'll see this change some day.

— Which upcoming or not well-known features of Ruby language would rush in future?

— I look forward to strings becoming immutable-by-default, as they are in most other languages. Parallel programming would be much simpler if more of Ruby's objects supported pure-immutable or "deep freeze" semantics. It's a bit like the Rust ownership model...if you're going to be sharing an object across threads, choose the version of that object that you know can't be modified anymore. This extends to arrays, hashes, and just about every other mutable object in Ruby: we need to make it easier to lock down mutable data.

— Could you give me an advice on how to move my ancient monolithic project to JRuby? And should I?

— The first question really is whether such a move would benefit you. There's many good reasons to consider a move to JRuby:

  • Reducing CPU  and memory costs in a shared hosting environment by utilizing JRuby's true parallel threading
  • Deploying a Ruby application into a JVM-heavy environment, such as used by larger financial or government organizations
  • Needing access to libraries that only exist on the JVM, or that are more portable or scalable on the JVM than their Ruby or C equivalents
  • Getting a little performance boost out of CPU-heavy or concurrency-heavy applications.

— I would say if your application is scaling well and not costing you too much today, perhaps you don't need to make a move. But if you decide you need more out of Ruby, here's the process for migrating:

  • Do a clean bundle of your application, paying special attention to C extensions you may be using. You can also do this bundling *on* JRuby, and then deal with missing or unsupported libraries one by one.
  • For each extension, search for a JRuby equivalent. We have some pages on the JRuby wiki to help with this. Most popular libraries have JRuby versions. If no JRuby version exists, you may look for a pure-Ruby version (it might be fast enough on JRuby) or a JVM library (in Java or Scala or Clojure or whatever) that could be used as a replacement.
  • Once your bundle completes, you should have a working JRuby application! We've worked very hard on compatibility, and try to be responsive if users find new issues, but a successfully-bundled application is expected to work.

The steps beyond this involve deciding how to take advantage of your newfound power: how many threads to throw at a given server, what you're going to do with all the money you're saving, etc.

— What should nowadays students learn to become good programmers?

— When I was at university, my earliest computer science courses used the Scheme language, a Lisp-like functional language that's great for teaching the fundamentals of programming. I still recommend that serious new programmers work through at least some of the Structure and Interpretation of Computer Programs book from MIT. Beyond that, I'd say learn as many different and unusual languages as you can; they'll all give you new ideas and new ways to look at programming problems.

— How do you keep yourself motivated for programming? Have you ever been "burned-out"?

— Burn-out is a real problem in our industry, and working in open source brings with it huge amount of stress. We've all felt that way sometimes...too much work to do and not enough time to do it, missing out on time with family and friends, ignoring our own health so we can fix one more bug. These days I try to center myself by keeping up with hobbies: playing video and board games, learning to play guitar, studying foreign languages, and traveling around the world to meet new friends. There's always this nagging workaholic telling me to get back on the job, but I'm learning how to maintain the right balance.

— What do you think about Russia and what do you expect of the upcoming RubyRussia event?

— I love Russia, and my speaking trips the past few years have been some of the most rewarding of my life. This will be my fourth visit, having been to Saint-Petersburg, Moscow, and Novosibirsk (!!!) previously. I'm looking forward to returning to Moscow and meeting the RubyRussia community I've heard so much about!

Questions by Dmitry Matveyev PM at Evrone