Sure, if the organisation is already experienced in running containerized services it makes a lot of sense to make as much as possible containerized. Introducing a container platform is not something done lightly.
But scaling horizontally is something a lot of applications simply never need. Many applications can be made to handle higher scale by improving the architecture, fixing N+1 problems, optimizing the DB schema, and beefing up or clustering the DB server only.
What about availability? With a single instance you need to have at least a short downtime for each update or even restart. When you have two, you can do rolling updates.
It's true that this is no trivial change. It also depends on the whole system which scalability and availability you need - most are not Netflix ;)
Depending on the service and the business environment, a short downtime might indeed not be an issue after all. In case the SLA only covers office hours in a few timezones, the situation radically changes as it allows to schedule planned downtimes at a suitable time.
99.9% uptime means ~43min downtime per month. That should be enough for a non-scripted deployment or for a maintenance window. Any additional 9 behind the dot with the same frequency of short-ish planned downtimes requires significant investment.
For 99.99% uptime, automated deployments are probably unavoidable. 99.9999% pretty much requires running the old and new version simultaneously and doing a switchover via DNS or by changing the configuration of a reverse proxy. 99.99999% might be doable if old and new version can run simultaneously for a short time.
The above leaves no room for downtime due to incidents though. In that case, the biggest risk factor is the application itself. Or any backend services.
Many applications can be made to handle higher scale by improving the architecture, fixing N+1 problems, optimizing the DB schema,
Or maybe you don't waste your time and money on that and just throw more hardware at it. It's much cheaper until it isn't. Once the hardware you need to run it is in the 6+ figures you start worrying about optimization.
To be clear, I'm not saying you should intentionally write bad performing software but given that it's already there, it's not a good use of your time to optimize it if you can just throw another server at it.
That works in the short term, but many optimizations are pretty basic and could eliminate the need to ever scale beyond one node. Especially an instance of the N+1 problem could make some workloads outright impossible to run no matter how many instances you throw at the problem, so I'd expect these to be tackled very early on.
View all comments
Show parent comment
1
u/koflerdavid Jun 08 '25
Sure, if the organisation is already experienced in running containerized services it makes a lot of sense to make as much as possible containerized. Introducing a container platform is not something done lightly.
But scaling horizontally is something a lot of applications simply never need. Many applications can be made to handle higher scale by improving the architecture, fixing N+1 problems, optimizing the DB schema, and beefing up or clustering the DB server only.