Django REST framework vs Grape: What are the differences?
Developers describe Django REST framework as "Web APIs for Django". Django REST framework is a powerful and flexible toolkit that makes it easy to build Web APIs. On the other hand, Grape is detailed as "An opinionated micro-framework for creating REST-like APIs in Ruby". Grape is a REST-like API micro-framework for Ruby. It's designed to run on Rack or complement existing web application frameworks such as Rails and Sinatra by providing a simple DSL to easily develop RESTful APIs. It has built-in support for common conventions, including multiple formats, subdomain/prefix restriction, content negotiation, versioning and much more.
Django REST framework and Grape can be primarily classified as "Microframeworks (Backend)" tools.
"Browsable api" is the top reason why over 54 developers like Django REST framework, while over 3 developers mention "Well documented" as the leading cause for choosing Grape.
Django REST framework and Grape are both open source tools. Django REST framework with 14.6K GitHub stars and 4.33K forks on GitHub appears to be more popular than Grape with 8.87K GitHub stars and 1.09K GitHub forks.
According to the StackShare community, Django REST framework has a broader approval, being mentioned in 159 company stacks & 79 developers stacks; compared to Grape, which is listed in 11 company stacks and 7 developer stacks.
What is Django REST framework?
What is Grape?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
Zulip has been powered by Django since the very early days of its development with Django 1.4, back in 2012. As a reasonably mature web application with significant scale, we're at the stage in many companies' development where one starts to rip out more and more of the web framework to optimize things or just make them work the way we want. (E.g. while I was at Dropbox in early 2016, we discovered we only had about 600 lines of code left from the original Pylons framework that actually ran).
One of the things that has been really fantastic about Django is that we're still happily using it for the vast majority of code in the project, and every time Django comes out with a new release, I read the changelog and get excited about several improvements that actually make my life better. While Django has made some design decisions that I don't agree with (e.g. I'm not a fan of Django REST framework, and think it makes life more difficult), Django also makes it easy to do your own thing, which we've done to great effect (see the linked article for details on our
Overall I think we've gotten a ton of value out of Python and Django and would recommend it to anyone starting a new full-featured web application project today.
Django REST delivered all the content to the BI, making calls to the Postgres DB, aggregating numeric data, and automatically associating data models at the time of row creation.
Instead of using Django for both back and frontend, I use DRF to layout an API that ReactJs can pull data from. Easy to setup, well documented, and works seamlessly with React.
django에서 api를 만드는데 최고의 framework라고 생각합니다. 아직은 tutorial 수준의 class base view, function base view 수준으로 사용합니다.
하지만 현재 진행중인 프로젝트의 심화로 REST framework를 심도있게 다룰 예정입니다.
Really great framework for building RESTful APIs. Lots of plugins for it!