4 ms·
This is mostly true if your application is mostly CRUD with HTML endpoints (the use case Django was designed for), particularly very "solved" use cases like blo
by CuriouslyC 11y ago
This is mostly true if your application is mostly CRUD with HTML endpoints (the use case Django was designed for), particularly very "solved" use cases like blogs.
(As an aside, for very crud-heavy applications that are client-heavy with primarily JSON data endpoints, I suggest using PostgREST if possible. It is almost certainly going to be better than any CRUD API you produce yourself)
If your application is mostly endpoints that do "interesting" stuff, you aren't going to hit much of the Django infrastructure, and piece you are most likely to hit (the ORM) is so far behind the dominant Python ORM (SQLAlchemy) that it is just painful.
Flask is a lot better at getting "out of your way" than Django. The main problem I see with flask is that it isn't obvious to people picking up the library the right way to structure and scale an application code base.
- wcarss 11y ago> The main problem I see with flask is that it isn't obvious to people picking up the library the right way to structure and scale an application code base. I wholeheartedly agree! Do you have any resources in mind (even perhaps not specific to flask) that you think would be useful to people hitting that wall?
- mixmastamyk 11y agoThese came up last week: https://etscrivner.github.io/posts/2014/10/building-large-flask-apps-in-the-real-world/ https://etscrivner.github.io/posts/2014/10/building-large-fl... https://news.ycombinator.com/item?id=11121355 https://news.ycombinator.com/item?id=11121355