171–180 of 330 posts
Earlier quoted context omitted.
$2k? That’s a $100k project for a medium size Corp
hmm where did you get the numbers? (what's "medium-size corp" and how did you come up with $100k ?)
Regardless of the cost and capacity analysis, it's just hard to fight the industry trends. The benefits of "just don't think about hardware" are real. I think there is a school of thought that capex should be avoided at all costs (and server hardware is expensive up front). And above all, if an AWS region goes down, it doesn't seem like your org's fault, but if your bespoke private hosting arrangement goes down, then…
Earlier quoted context omitted.
As long as you also include the Cloud Certified DevOps Engineer™[0] to set up that RDS instance. [0] A normal sysadmin remains vaguely bemused at their job title and the way it changes every couple years.
It's also interesting that the cloud engineer can apparently be both a DBA, network-, storage- and backup engineer, but if you move the same services on-prem, you apparently need specialists for each task. Sometimes even the certified cloud engineers can't tell you why an RDS behaves the way it does, nor can they really fix it. Sometimes you really do need a DBA, but that applies equally to on-prem and cloud. I'm a s…
One of the more detrimental aspects of the Cloud Tax is that it constrains the types of solutions engineers even consider. Picking an arbitrary price point of $200/mo, you can get 4(!) vCPUs and 16GB of RAM at AWS. Architectures are different etc., but this is roughly a mid-spec dev laptop of 5 or so years ago. At Hetzner, you can rent a machine with 48 cores and 128GB of RAM for the same money. It's hard to overstat…
Earlier quoted context omitted.
A fair comparison would include the cost of the DBA who will be responsible for backups, updates, monitoring, security and access control. That’s what RDS is actually competing with.
You don’t need a DBA for any of those, you need someone who can read some docs. It’s not witchcraft.
Regardless of the cost and capacity analysis, it's just hard to fight the industry trends. The benefits of "just don't think about hardware" are real. I think there is a school of thought that capex should be avoided at all costs (and server hardware is expensive up front). And above all, if an AWS region goes down, it doesn't seem like your org's fault, but if your bespoke private hosting arrangement goes down, then…
the benefits of don't write a distributed system unless you really have to are also very real
A lot of the time businesses just aren't that important. The amount places I've seen that stress over uptime when nothing they run is at all critical. Hell you could drop the production environment in the middle of the day and yes it would suck and you'd get a few phone calls but life would go on. These companies all ended up massively increasing their budgets switching to cloud workloads when a simple server in the…
Just today I wasted some time due to an unexpected Tailscale key expiry and some other issues related to running a container cluster: https://blog.kronis.dev/blog/the-great-container-crashout Right now, my plan is to move from a bunch of separate VPSes, to one dedicated server from Hetzner and run a few VMs inside of it with separate public IPs assigned to them alongside some resource limits. You can get them for pre…
Give me a box, trust me with ssh keys and things are so much easier. Simple is good for the soul and the wallet.
Earlier quoted context omitted.
> don't you think it's highly unlikely that someone will stumble over the power cable in a hosted datacenter like hetzner? You're not getting the point. The point is that if you use a single node to host your whole web app, you are creating a system where many failure modes, which otherwise could not even be an issue, can easily trigger high-severity outages. > and even if, you could just run a provisioned secondary…
Do you actually think dead simple failover is comparable to elastic kubernetes whatever?
References to "elastic Kubernetes whatever" is a red herring. You can have a dead simple load balancer spreading traffic across multiple bare metal nodes.
Is there something obvious that I'm missing?