You need database HA and load balancers on day 1?

You must be doing truly a lot of growth prior to building. Or perhaps insisting on tiny VMs for your loads?

swiftcoder 5 days ago | parent | next [-]

> Or perhaps insisting on tiny VMs for your loads?

This happens way too often. Early-stage startups that build everything on the AWS free tier (t2.micro only!), and then when the time comes they scale everything horizontally

	▲	throwaway7783 4 days ago \| parent [-]
		I'll repeat what I said above. It's for availability (aka I don't want my customers screaming at me if the machine goes down). And no , scaling out was not our first solution, scaling up was. I have considered going bare metal so many times, but the number of things we need to build/manage by ourselves to function is too much right now. Hopefully when we can afford to do it, we will.

▲

throwaway7783 4 days ago | parent | prev [-]

HA is for availability. I don't want downtime for my enterprise customers. Are your customers okay with downtime? And as soon as you have more than one nodes, you need some kind of a load balancer in the front.

▲

rcxdude 3 days ago | parent [-]

In practice, until you're at a certain scale, software bugs are more of a threat to your availability than hardware failures or maintenance downtime, and the cloud does nothing for you there (in fact, the additional complexity is likely to make it worse). Modern hardware is pretty reliable, more so than a given ec2 instance, for example.

	▲	throwaway7783 2 days ago \| parent [-]
		Often, software bugs cause issues with machines (uncontrolled logging overwhelming disk space and killing everything, instead of objectstore absorbing it, or a memory bug that kills the process over a few days and needing manual or custom monitoring scripts instead of k8s handling this until its root caused, and so on)