Is Django a good solution for creating applications that won't use any database and communicate only through an internal API?
closed as primarily opinion-based by MichaelT, Dan Pichelman, Kilian Foth, ratchet freak, gnat Nov 17 '14 at 10:36Many good questions generate some degree of opinion based on expert experience, but answers to this question will tend to be almost entirely based on opinions, rather than facts, references, or specific expertise. If this question can be reworded to fit the rules in the help center, please edit the question. |
|||||||||||||||||
|
Depends what you call 'good'. However, while you can use django with no database, the object-relational mapper is pretty much its first and foremost advertised feature. Django was designed to produce database-backed web sites, so if you're not going to use a database you might end up dealing with a bunch of unnecessary hassle. |
|||
|
Django comes with inbuilt sqllite database. Which doesn't require much configurations. And when it comes to the use django without database then it simply violates the MTV pattern of Django. |
|||||||||
|
Although there is nothing stopping you from not using a DB in Django, my advice would be: "If you don't need a full stack framework, don't use a full stack framework". Python has many excellent microframeworks that might suit your needs better. This blog post discusses some of them: http://www.konstruktor.ee/blog/python-web-framework-roundup My personal favorite is Flask: http://flask.pocoo.org/, but I have not done much real work with it. |
|||||
|
From the Django book:
You can use the framework to make a site with some logic in it, but you will be wasting some of its potential. Besides, interacting with the database from Django layer is too easy to ignore it. |
|||
|