Why Choose Flask over FastAPI
pythonkitchen.com
pythonkitchen.com
For a minimal microservice, something based on asyncio really is preferable. Flask doesn't do async IO. I don't really care if it is as fast as Go or node, but non-blocking matters. On the other hand, what Django brings to the table also matters. I much prefer using the kitchen sink offered by Django rather than bolting on bits and pieces to a Flask or FastAPI solution.
One notable exception is OctoPrint, which uses Flask. It's designed to run on Raspberry Pis with limited resources. Maybe it would be better off with FastAPI now but it started on Flask when FastAPI didn't exist, and Django would probably have been too heavy and opinionated in that scenario.
asyncio won't do much for you if your application is CPU-bound. (Admittedly, that's usually not the case with network services)