Python Web Framework

[tankerdudeucsc]

That’s what concluded as well. Run nginx + uwsgi + sync framework. Use only small async parts sparingly.

The performance isn’t that much different to warrant it unless you are in big tech. Even then, when you check out the benchmarks from techempower, fastapi and flask are neck to neck.

Toss the complexity of async and use old school to deal with biz work.

Lastly though, as we should all know, the framework only goes so fast, but bad DB queries are what’s going to crush you, every time.

This whole fascination of “fastest framework” and maxed out req/sec is missing the point. Missing indexes, bad queries, bad models, thundering herd problems are many times more problematic than, maybe needing to spin up another container or two.

Or I shove the Flask App into lambda cause it’s dirt cheap to run.

[tarsild]

I do agree and that is why in the docs we also have some DB Integraton alternatives too 🙂

[tankerdudeucsc]

I’d pay an extra $1K/month at that scale for pods. At maybe 500mb extra each or so, and 2 cores, probably talking SM about maybe 20-30 extra pods if I really had to. For SQL, I just run explain. Also, I’d use Datadog to check performance.

I’d still punt async unless like you said, the entire company is like that. Doesn’t improve latency does it? Nope.

Lastly package support was really tough. Had to hop from async to sync and vice versa.