Python/Django REST API Architecture

Question

I'm trying to build a niche social network like Instagram as a Python/Django application.

So the things I need, regarding architecture, are (I guess):

REST API (e.g. api.mystagram.com).
Public website (www.mystagram.com or mystagram.com).
URL shortener (e.g. mystagr.am).
Android app
iPhone app
Windows Phone app
...

Before this I only built simple to some less-simple websites, but never extremely complex with own custom APIs or so. I have never build my own REST API before (I have used other REST APIs though) or even built an Android/iPhone app and distributed it in the Play Store/App Store (I have made some typical hello world examples though).

So, the most important thing to me seems to create a kick-ass REST API first and proceed from there. I am blocked however by a few questions.

How should I organize the projects for the public website and REST API? Should these be separate Django projects or should I create only one Django project and add both the public website and REST API as an internal Django module?
Should the public website also make use of the REST API? Or is it better to just use the plain Django models for this?

Thanks in advance for any help! If somebody knows some great presentations or so on this topic (architecture), always welcome!

Kind regards, Kristof

The Django REST framework will probably help you get started. django-rest-framework.org — cjd82187
– cjd82187, Commented Sep 5, 2013 at 19:15
Definitely use something like Django REST Framework or Tastypie. They will be part of your django project and will use your existing models. You can use it on the public site as well especially if you want to do a lot of ajax stuff. — Ngenator
– Ngenator, Commented Sep 5, 2013 at 19:25

stormlifter · Accepted Answer · 2013-09-05 19:36:54Z

9

Django REST Framework

https://github.com/tomchristie/django-rest-framework

Very well maintained, great documentation, easy to use.

answered Sep 5, 2013 at 19:36

stormlifter

3,8713 gold badges19 silver badges20 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

Robin · Accepted Answer · 2013-09-05 19:15:32Z

1

I think Tastypie will do what you want. And its simple and easy. Check this out - http://django-tastypie.readthedocs.org/en/latest/!

answered Sep 5, 2013 at 19:15

Robin

5,51617 gold badges59 silver badges89 bronze badges

3 Comments

Braek Over a year ago

Thanks for the tip! I also found django-rest-framework.org earlier today. This may sound like a stupid question, but is it recommended to use REST frameworks like these or is it better to create your own implementation? Since REST is not really a standard...

stormlifter Over a year ago

Well I recommend you use Django REST Framework. Mostly because you already use Django and realize the benefit of being able to focus on your app.

Braek Over a year ago

OK - I'm playing with the Django REST Framework as I speak. Thanks for the tip.

Zulu · Accepted Answer · 2017-01-01 23:22:26Z

0

To Answer your first question, It would be good practice to put public web site and REST APIs into one django project. Now days every web application contains public web site as well as rest apis for mobile app. So it would be easier to maintain both website and rest apis if they both in one application. Below is Django REST Framework link. https://github.com/tomchristie/django-rest-framework

For second question, Yes you can use rest apis in website also. But in general you don't need to do it. In most of the cases django model works for you.

edited Jan 1, 2017 at 23:22

Zulu

9,3539 gold badges51 silver badges57 bronze badges

answered Nov 23, 2015 at 17:06

Jayesh Vaghasiya

2142 silver badges7 bronze badges

Collectives™ on Stack Overflow

Python/Django REST API Architecture

3 Answers 3

Comments

3 Comments

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

3 Answers 3

Comments

3 Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Related