Difference between Pluggable Views and Blueprint in Python Flask
As far as routing goes, Pluggable Views (aka class-based views) is far more superior than Blueprints, which are just a bunch of functions with routes decorators.
In Pluggable Views paradigm, it facilitates code reuse code by organizing view logics in classes and subclass them. URL routes are registered with app.add_url_rule() call, this is great because it follows the S in SOLID principles (separate of concerns). In Blueprints approach, each front end view logic are encapsulated within the view functions, which aren't suited well for code reuse.
What's the difference between PluggableViews and Blueprint in Python Flask?