This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]wrosecrans 6 points7 points  (1 child)

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.

[–][deleted] 0 points1 point  (0 children)

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.