> An example of where this excess bloat would be bad is in a microservice architecture. Django is pretty easy to slim down. Yank the middleware you don't need,

> An example of where this excess bloat would be bad is in a microservice architecture. Django is pretty easy to slim down. Yank the middleware you don't need, stick to what you do. No need for stuff like context processors if you are using DRF. You don't have to use models or the ORM at all if you don't want. I think the line count would be very similar for many cases. For example, if your flask app needed DB access, you'd end up pulling in and boilerplating an ORM anyway. Ditto for sessions/authentication/etc.