Building Large Flask Apps in the Real World
&gt; In the end you should be aiming to design your application to depend on Flask as little as possible.<p>I&#x27;m 3 years in to a project where I&#x27;ve taken the approach of having my &quot;app&quot; as its own package. Flask is then a thin wrapper that instantiates the app and then exposes the views to talk to it. I handle validation &#x2F; sessions &#x2F; config etc within Flask.<p>It&#x27;s extremely flexible. I have some stuff that runs off as worker processes. No problem - the core is the same, the wrapper around it is different. I also have a boot.py that I can call so I&#x27;m working directly with the app in ipython (again, it&#x27;s a wrapper that starts the app).<p>I&#x27;m currently reworking the structure for capacity planning, which is mostly just a matter of splitting the Flask app into 2 apps for handling different parts of the work.<p>Because my core app is decoupled from the web app it&#x27;s all really easy to do.