The way models, serializers, and viewsets are defined and work together is, AFAIK, non-existent in the JS world.
Even Ember, which IMO is the best candidate for becoming a full-stack framework, does not have all the bells and whistles that come with Django's ORM.
[0] http://www.django-rest-framework.org/tutorial/quickstart/
https://docs.djangoproject.com/en/1.9/
The docs are amazing, probably because Django was created by journalists so they are really great at communicating things. It's not like most programming docs that leave you feeling lost and need to be supplemented with outside tutorials.
That said I'm new to programming so I supplemented the tutorial and instructions on the docs page with the one on the Django girls site.
http://tutorial.djangogirls.org/
I found that between these two and occasional references to stacks when I felt lost, it was all I needed.
For example, the first page of the "real" tutorial covers serialization in depth: http://www.django-rest-framework.org/tutorial/1-serializatio...
Since you're looking for an alternative to RoR, I'm assuming you want Django. They have great docs and you might check out godjango.com
And regarding Django being the killer app: There are other people for which numpy/scipy is Python's killer app, for example.
But if your use case fits well within the Django ecosystem...then Django can be easier.
http://www.oracle.com/technetwork/developer-tools/rest-data-...
Otherwise, it's smooth enough and runs in Tomcat.
I haven't used the REST features so much; we just use for the APEX pl/sql bridge (ugh).
AFAIK this is deliberate and opinionated.
See for yourself.
I can't find a way to make a one time donation. Anyone know how?
DRF is one of the core reasons why Django is top choice among web frameworks today. In my opinion, it sets the standard for rest frameworks for the development community at large.
Most of my experience with it has been great though, it's a very well built technology.
For a helpful reference also check out http://cdrf.co
If you're familiar with Rails it's like https://github.com/rails-api/rails-api which was recently merged into Rails in v5.
You could totally add a graphql endpoint to any api `/graphql?[your GQL query here]`. We're currently exploring adding that to our Django/DRF backend with one of these https://github.com/chentsulin/awesome-graphql#lib-py
I build my apps on GNU/Linux, deploy via Apache, and use Django (with DRF) and Ember.
So how does "GLADE stack" sound?
https://www.reddit.com/r/django/comments/2ijyuq/added_tom_ch...
* Ruby Together - https://rubytogether.org/
* Django Fellowship Program - https://www.djangoproject.com/fundraising/
* Read the Docs sponsorships - http://read-the-docs.readthedocs.io/en/latest/sponsors.html
I think the business case is clear enough to make for a big project like REST framework. It's a relatively small investment per-company, but the relative payoff if we can hit a level that keeps it sustainable is huge.
The team I was previously with used Core API in some of https://www.crunchboards.com/
That's got a service-based architecture, and we were using it both on the server side (where we wrote explicit Core API schemes, rather than auto-generated) and on the client side (moving towards doing our inter-service communication using `coreapi`, rather than directly through `requests`.)
For us, the dynamic client libraries were a big win - the client code that you're working with becomes more meaningful and robust, as it's working with an application layer abstraction, rather than directly at a network layer.
Django Channels is coming in 1.10 which will make realtime better.
I know that's maybe not the most exciting change, but I think it's important that it be very obvious what the code does even if a person isn't an expert in a given technology, especially when there are privacy/security implications.
Awesome project, we're supporters!
