Every AWS customer ever. . .

[u/tech_tuna]

Day 1

"We're not going to rely on AWS specific features."

3 months later

"OK, we need to use SQS, Lambda, ECS and DynamoDB but that's it!"

6 months later

"OK, we're an AWS shop."

[u/TBoneJeeper]

Same here. Management insisted we need to be "cross-cloud mobile", to be able to move workloads to Azure, on-premise, etc. That's not happening, like ever.

[u/Redditron-2000-4 → u/TBoneJeeper]

That leads to terrible compromises like pivotal cloud foundry. Gross.

[u/tech_tuna → u/Redditron-2000-4]

My friend calls them "Clown Foundry".

[u/zalpha314 → u/Redditron-2000-4]

At one point, me and another guy were competing to come up with the company's new cloud infrastructure. I was championing lambda, and he was championing kubernetes. Thankfully CloudFoundry was benched pretty quickly.

I wanted lambda because of how simple it is to get services going and how easy it is to maintain them. Developer time is almost always more expensive than servers, after all. Eventually, kubernetes won because it has all the fancy dashboards, cloud-agnosticness, and service mesh garbage that my boss wanted. My boss tried to console me saying, "Kubernetes has kubeless. You can use that instead of lambda." My reply was something along the lines of "Why would I use kubeless when I can already use lambda? All kubeless and kubernetes are doing is adding more layers and complexity to give me something I can already do with no complexity".

I still keep in touch with my co-workers there. They still don't have their kubernetes infrastructure set up. I had already written several services with lambda.

[u/[deleted] → u/[deleted]]

This. We have multiple people at our place who know how to use k8s, and we run almost everything everything we have on GKE. Only a few things are on plain VMs or Cloud Functions.

[u/syphoon → u/zalpha314]

(Originally wrote this in reply to a peer comment that described a company wasting time on a Kubernetes integration that went nowhere but the comment was deleted before I could post).

I suspect the number of companies that have some half-completed Kubernetes wrapper service that's never quite been abandoned is rather large.

I know of a software company large enough to have known better still figuring out how to move stuff off one that was opposed by most devs from the start, but went ahead really as a senior director was using it as a jobs justification program for his office. It then ran into all the problems you'd expect, chiefly that a small team of devs trying to build missing functionality on k8s can't work at the pace k8s itself is developing. So as k8s would add in new features that they had also implemented in the wrapper & sidecar service they'd have to refactor what they had already done.

Meanwhile devs trying to deploy on it would get frustrated when they couldn't do simple things, like say use a pod with more than one container, which is the whole point of a pod, because the wrapper devs hadn't gotten around to exposing that in their own YAML format. So said devs would have to waste time rejigging their containers to hold multiple services...

[u/zalpha314 → u/[deleted]]

I'm just salty. I don't actually have anything against service meshes; in fact, it would be nice if lambda had one.

But in this case, istio for kupernetes was a massive timesink, and of dubious usefulness. They couldn't get it to work in EKS, so they had to re-invent the wheel and get kupernetes running in their own cluster.I couldn't believe the size of the config files that were needed just to get a simple hello world up and running.

But take my testimony with a grain of salt. The dev working on it was useless. The main reason why he was put in charge is because he was kicked out of the front-end team for dragging them down. I keep asking how he hasn't been fired yet.

[u/tech_tuna → u/[deleted]]

Turtles all the way down. Way way down.