Counterpoint, and let's assume mostly parity of flask :: sinatra and rails :: django. I've usually used Flask and even when I needed a few db operations you co

Counterpoint, and let's assume mostly parity of flask :: sinatra and rails :: django. I've usually used Flask and even when I needed a few db operations you could easily contain that to a small part of the code and stepping up to django would have felt like a huge step up in complexity. But I guess it really depends on what you're actually writing - your use case sounds a bit like "something like wordpress" from a "customer uses this" point, and mine were mostly "small REST API endpoint for something".