Both the above mentioned frameworks offer support for non orm data resources.
See tastypie's official docs on how to use it with riakdb [1] .
And I have also used django rest framework to relay RESTful APIs for a django app which uses restful apis from a locally running REST server.
So the data source here wasn't rdbms or non-rel db but json feed from local web server.
Since this server had a django based web interface which consumed these APIs , and we couldn't expose this directly to web as it expose lots of level and raw data.
Whereas the django based web app offered limited functionality that we would like to offer clients with api as well.
Rolling out authenticated public facing restful APIs with django made more sense .
Using these frameworks I am under the impression that I could develop product faster as compared to rolling out my own APIs and authorization and authentication is less complex as already there are very good existing django apps that ease the job (dry) :-)
Just my thoughts :-)
[1] - http://django-tastypie.readthedocs.org/en/latest/non_orm_data_sources.html
Thanks Rahul,
I thought about that.
I do not need Django's ORM as I do not use relational db and I do not need Django's Templates as I use rest api. So I am not sure what value does django add in my case?
On Sunday, June 30, 2013 12:24:28 AM UTC-7, Rahul Gaur wrote:--Hi,
What about change-tastypie or django-restframework or something similar ?
As a part of my GSoC project [1] , I am implementing a project sharing web site with social features.
I need RESTful APIs so that the functionality of the site could be integrated into SugarLabs [2].I am planing to use Django with one of the above rest frameworks to serve RESTful APIs and a web client in backbone.js which will consume the APIs as well.
[1] - https://github.com/aregee/moksaya
[2] - http://sugarlabs.orgOn Jun 30, 2013 12:13 PM, "zweb" <ashis...@gmail.com> wrote:
I am writing an Python application which will expose REST API. It will be client agnostic. In future I will provide a Web client and a mobile client and may be a rich desktop client. These clients will connect to application using the REST api only.
Should I use Django for this? or is Django for Web based applications only as it is web framework. What advantage does Django brings in such a architecture.
Would it be much simpler if I use simple python with some python rest web services framework on top of it instead of Django?
I am a big fan of Django but not sure if a Web framework such as django is good fit for REST Services based architecture. I not building a (monolithic) web application.
--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users...@googlegroups.com.
To post to this group, send email to django...@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
For more options, visit https://groups.google.com/groups/opt_out.
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
For more options, visit https://groups.google.com/groups/opt_out.
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
For more options, visit https://groups.google.com/groups/opt_out.
No comments:
Post a Comment