3 ms·
You absolutely can use a graph DB in Django. But if you're not using a relational DB as your primary datastore (for stuff like authentication and authorization)
by espeed 15y ago
You absolutely can use a graph DB in Django. But if you're not using a relational DB as your primary datastore (for stuff like authentication and authorization) and not using the ORM, how much of Django would you really use?
Django was built around an ORM. Now you have more database options that have less of an impedance mismatch, but because Django is so ORM-centric, forgoing the RDBMS in favor of another option means you now have a framework mismatch.
Starting with Flask, which was designed to be decoupled, simplifies things.
- simonw 15y ago"How much of Django would you really use?" The URL mapper, the view abstraction, the middleware, the debugging tools, the generic views concept, the httprequest and httpresponse classes, the templating system, the caching framework, the syndication library and a bunch of the third party ecosystem tools.
- espeed 15y agoAhh...what you describe sounds a lot like Flask.
- parfe 15y agoIt sounds like every halfway decent web framework ever written.
- espeed 15y agoThe point is why not just start with Flask if that's the feature set you're going to end up with.
- hello_moto 15y agoBecaus I'm more familiar and have experienced in using it. Because I decided to use Django for the other part of my big web application. Because I want to learn more and get better with my tool as opposed to learn the Python web app framework of the week.
- deleted 15y ago[deleted]