Kubernetes Was Overkill. We Moved to Docker Compose and Saved 60 Hours

Hi! I noticed you mentioned launching pico balloons on a different thread. I launched two of them using these [1] balloons but they both burst within hours of launch. Do you have any advice for me? Did you pre-stretch the balloons? I just unfolded them and filled them up to about 6 grams of free lift before launch.

[1] https://balloons.online/orbs-32-clear/

> Month 2: The Cracks Start Showing > First production issue: a service kept crashing with OOMKilled errors. > ... > I spent three hours figuring out: > ... > What the difference between requests and limits even means

so he says before this he wouldn't shut up about k8s, but obviously didn't even read the documentation.

how do you expect to use a tool as encompassing as k8s without even understanding basic concepts?

give these guys an airplane and they will start googling how to take off when they are already speeding up on the runway.

You can look at the authors LinkedIn page and see that he’s never worked for a startup. The only job he’s had for more than 14 months was at Huawei.

I’m pretty sure this is all completely fabricated LLM slop, created as a vehicle for the “handbook” adverts littered throughout.

1. https://www.linkedin.com/in/devrimozcay

I agree, I personal prefer simple docker runtimes over orchestration systems

Newbies started on 2 node docker compose setup and went to production with a system they didn't understand and then had a bad time, blame the tool first... color me surprised?

Kubernetes solves problems, but you have to know your tools instead of saying they are not good or are overkill. Compose won't take you to scale, spend time learning an industry standard before you run it in production