Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Zero-Downtime Deployments with Docker Compose – No Kubernetes Required

statusdude.com

Post reply on HN
Print view View original

31–40 of 81 posts

Re: Zero-Downtime Deployments with Docker Compose – No Kubernetes Required

#31

Post by canto »

variety8675 wrote: post #10

> There's a mass delusion in the industry that you need Kubernetes to run a serious production service. You don't. At StatusDude, we serve thousands of monitoring checks per minute, run multi-region workers, and deploy multiple times a day This is pretty small scale, Kubernetes comes in when you've got a larger workload.

While I agree with you I'm not sure the rest of the world does.

Over the past decade, I'm seeing k8s used everywhere for everything, companies setting up clusters to run literally one simple app with couple of hundred requests per hour.

Re: Zero-Downtime Deployments with Docker Compose – No Kubernetes Required

#33

Post by alexaholic »

bijowo1676 wrote: post #18

so op just recreated with sticks and tape a very basic feature what k8s does out of the box, and nobody else would be able to support his creation, because its handrolled adhoc with sparse documentation. sounds like ghetto engineering

[flagged]

Re: Zero-Downtime Deployments with Docker Compose – No Kubernetes Required

#34

Post by bijowo1676 »

alexaholic wrote: post #33
bijowo1676 wrote: post #18

so op just recreated with sticks and tape a very basic feature what k8s does out of the box, and nobody else would be able to support his creation, because its handrolled adhoc with sparse documentation. sounds like ghetto engineering

[flagged]

I am not sure the argument "muhh k8s is too complex, I will roll docker instead" flies well in the age of cloud managed k8s offerings

EKS is literally one click of a button away and you dont need to handroll this.

even if you dont know AWS console nor terraform, claude code with aws mcp can do that for you

Re: Zero-Downtime Deployments with Docker Compose – No Kubernetes Required

#35

Post by zzyzxd »

bijowo1676 wrote: post #18

so op just recreated with sticks and tape a very basic feature what k8s does out of the box, and nobody else would be able to support his creation, because its handrolled adhoc with sparse documentation. sounds like ghetto engineering

If this creation stays as is, then it's not very complicated and pretty easy to understand and support. But that is a big IF, and very likely won't be true. Over time people will add more useful features to it, then it becomes another Kubernetes (and if you don't have a strong engineering team, it will probably be much worse than Kubernetes).

Re: Zero-Downtime Deployments with Docker Compose – No Kubernetes Required

#36

Post by switchbak »

bijowo1676 wrote: post #34
alexaholic wrote: post #33

Earlier quoted context omitted.

[flagged]

I am not sure the argument "muhh k8s is too complex, I will roll docker instead" flies well in the age of cloud managed k8s offerings EKS is literally one click of a button away and you dont need to handroll this. even if you dont know AWS console nor terraform, claude code with aws mcp can do that for you

I worked at a place (a big name in a given vertical!), where the SRE looked at K8S and said "hold my beer".

Out came Docker, dnsmasq, miles of duct tape and a whole lot of swearing. Just to come nowhere close to reinventing something better folks were doing years prior.

Just because you can (or think you can) doesn't mean you should. I sure do hope no one is maintaining that NIH monstrosity now!

Re: Zero-Downtime Deployments with Docker Compose – No Kubernetes Required

#37

Post by robmccoll »

bijowo1676 wrote: post #34
alexaholic wrote: post #33

Earlier quoted context omitted.

[flagged]

I am not sure the argument "muhh k8s is too complex, I will roll docker instead" flies well in the age of cloud managed k8s offerings EKS is literally one click of a button away and you dont need to handroll this. even if you dont know AWS console nor terraform, claude code with aws mcp can do that for you

The problem I have with Kunernetes in general is that everything is slow and configuring everything seems needlessly complex in common use cases.

Re: Zero-Downtime Deployments with Docker Compose – No Kubernetes Required

#38

Post by cyberax »

bijowo1676 wrote: post #18

so op just recreated with sticks and tape a very basic feature what k8s does out of the box, and nobody else would be able to support his creation, because its handrolled adhoc with sparse documentation. sounds like ghetto engineering

Perhaps we should look the other way: why use K8s if podman-compose can do the same? Maybe we should deprecate it and move towards simpler and more robust solutions?

Re: Zero-Downtime Deployments with Docker Compose – No Kubernetes Required

#39

Post by teliskr »

There's a mass delusion in the industry that using Kubernetes has to be hard, grossly over complex, and is always wrong if you are not Netflix scale. Is the system as described by the author significantly less complex and better than a small Kubernetes system? Sounds like they went through a lot of work to get it to their desired state.

Rolling your own zero-downtime deployments is as about as a good idea as rolling your own security... it's not a good idea.

I run our small system on a single EC2 instance with K3s. It runs a half-dozen or so services and does it quite well. I don't think it is particularly complex or over engineered. I like how easy it is to maintain the configuration in a helm package and quickly deploy it in different environments.

There is a learning curve for doing K8s well, but that's true for any non-trivial system.

Re: Zero-Downtime Deployments with Docker Compose – No Kubernetes Required

#40

Post by switchbak »

FearNotDaniel wrote: post #15
chmod775 wrote: post #9

Earlier quoted context omitted.

The reason most people reach for Kubernetes is because it's cool. The entire infra the vast majority of Kubernetes users have could run on a single bare metal machine with a second one for redundancy. To be fair: using Kubernetes anyways builds the skill just in case you become one of the 0.1% who actually need it down the line.

As soon as you work in a team, it’s irrelevant whether the project actually needs it. There will be someone who convinces stakeholders that it is necessary and then you just have to fall in line and learn the skills knowing that it is most likely one of the 99.9% of projects where it is just overkill.

Until your project has some success, and it turns out all those "complex" features actually turn out to be extremely useful.

Which is exactly what is happening with us, too bad we didn't choose K8S from the get-go and stuck with a "simpler" tool (gaining very little in the process).

Post reply on HN