I hear ya.

I’m an old school linux sysadmin. Been at it since 2003. I always groan when some higher-up wants us to host stuff on AWS and kubernetes, because they have no idea how stuff works, they just like the buzzwords and how everybody else is doing it this way.

And I’m just thinking, great. Instead of renting a very affordable beefy server with Hetzner or OVH, we instead use AWS which costs us 3-5x as much for less performance. And I try to explain to them, that not every application is like Netflix where you can just throw more nodes at it in order to scale.

Docker I like, since it can make things easier, with regards to ensuring a consistent environment, once you know your way around it. But kubernetes and AWS I hate with a passion. With AWS I can never truly know how much it’s gonna cost in advance, since their pricing structure is so mind boggingly complicated and you get billed even if so much as a fly farts in one of their server rooms.

Another thing is, every server provider that I’ve ever worked with, provides you with a means to boot a rescue mode if something goes wrong, so that you can fix it and reboot. No, with AWS, you need to make a snapshot, fire up another instance, attach that snapshot as a volume and mount it, then try and fix stuff, then shutdown that instance, detach that volume, then re-attach it using the same device name as the root device on your original instance. Oh, doesn’t boot? Rinse/Repeat. This shit can take hours. Whereas with a “normal” root server and a IPMI console and a rescue boot, it’s a question of minutes (usually).

Same with backups. I always ensure to create a backup system, so that I can restore certain files individually. Yeah, you can have automated snapshots of your EC2 Instance. But guess what, if something goes wrong, you boot the entire snapshot. So even if you just need to recover a single file, you still need to go through the process of reverting the entire system to a previous snapshot.

Bah, I could go on and on, but honestly the whole thing just seems to create more and more abstraction layers that just makes it difficult to figure stuff out when something doesn’t work.

The only thing, that I can somewhat appreciate with AWS is the ease with which you can migrate to a more powerful instance if you need it. Or how quickly you can launch a new instance. But thats about it.

In previous companies, we would have a couple of beefy servers that would run multiple apps on a single server, with perhaps a failover server being at the ready. Our server Budget was maybe 1-2k € per month.

With AWS it’s like 5x that.

honestly this just seems like venting based on your own experience of a terrible implementation that just so happened to be called “devops” in your company

Maybe if people spent a bit of time making producible environments and bundled stuff properly we wouldn’t be in this mess. DevOps is one of the side effects of the Docker virus and the “cool” architectures and stuff that is so complex that nobody can re-install/re-configure in a reasonable amount of time.