DEV Community

Discussion on: Don't marry the framework!

Collapse
ratulotron profile image
Ratul Minhaz

I agree with the idea of not tying your business logic with the framework as it surely locks you to that specific one, I never faced the problem of the framework changing its direction or core philosophy. As a back end engineer with a few years of experience in my belt, I can say most popular Python frameworks don't suffer the problem of the goal changing. For example, Django has been very consistent with its batteries included and DRY philosophy year after year. Yes, the framework evolved a lot since it's inception, but nothing that would require essentially an overhaul of your existing codebase. On the other hand, another popular framework Flask is simply a "micro framework", meaning apart from the core mechanics you are free to implement whatever you want. So you are free to do your thing without worrying about common middlewares like session management and caching.