How exactly does a python program scale? If you're at the point of receiving 10s of thousands of requests/minute, do you basically have a ton of python containers or vm's all running that a load balancer evenly divides work to?
There's no one answer to how to scale an application. You look at what's the worst part, and focus on that. You look at code changes, architecture changes, whatever moves the bottleneck somewhere else.
If all your Python containers need to talk to a single database/storage backend instance, adding more containers will only make your problem worse.
This is what differentiates good architects vs bad architects - you HAVE to ARCHITECT for your workload on the extremes of performance - when you’re not at the edge case all of the problematic characteristics of your workload are hidden by the fact that you’re only making ten requests a minute.
-28
u/higherorderbebop Sep 09 '22
What is the purpose of non blocking and the added complexity due to async if it doesn't lead to better peformance?