Kubernetes and back – Why I don't run distributed systems
1–10 of 43 posts
Re: Kubernetes and back – Why I don't run distributed systems
#2Seems like all the issues described here are with stateful application and running HA mongo. I don’t think these performance issues are really a result of K8s itself. I do agree backing stuff up in this situation isn’t easy. I think that’s why a lot of folks punt their stateful services to managed services.
Re: Kubernetes and back – Why I don't run distributed systems
#3People are getting confused, alot of open source software released by major players (Kubernetes, Next.JS (which is really just FBs take on react SSR), Microservice architectures), have no place in a company smaller than 100 people. But they use them anyways, and it ends up costing a ton of money for almost no business benefit.
Re: Kubernetes and back – Why I don't run distributed systems
#4These posts come up so frequently, people keep falling for buzzwords they don't understand and then start blaming the tech. Distributed systems are all cool and fun but use them as a last option when you have exhausted all other choices.
> I took a moment to calculate the cost of hosting my app on the K8s offerings of a Hyperscaler like AWS, Google or Azure just to figure out that this won’t be an option for me.
Clear signal that you can't justify the overheads. Cloud services are costly but in most cases you'll pay similar cost in terms of time and in some cases lot more if you pick something complex that you don't know about.
Re: Kubernetes and back – Why I don't run distributed systems
#5People are getting confused, alot of open source software released by major players (Kubernetes, Next.JS (which is really just FBs take on react SSR), Microservice architectures), have no place in a company smaller than 100 people. But they use them anyways, and it ends up costing a ton of money for almost no business benefit.
Vercel, netlify, AWS, and gke have great marketing
Re: Kubernetes and back – Why I don't run distributed systems
#6K8s requires either a (small) ops team to run it or using a hosted cloud solution. It's powerful and pays off when you have this, but if you can't afford to pay for the cloud hosting or hiring a team to do it, you're not going to get the benefits, you're not the target market.
Many products have a minimum size at which they are effective, no one is buying an Oxide rack for their homelab or side project, no startup going through YC is buying an IBM mainframe, because they are both obviously nowhere near the minimum effective size/complexity/spend. K8s is the same, and yet it seems to trip up so many people.
Re: Kubernetes and back – Why I don't run distributed systems
#7The question is whether the potential revenue growth justifies the growing technical complexity.
Re: Kubernetes and back – Why I don't run distributed systems
#8Running a self-hosted Mongo cluster is tedious and complicated task by itself. Mongo Inc isn’t incentivized to make it easy and user friendly because they have a cloud offering for you.
In addition to that Kubernetes isn’t really tailored to stateful workloads, so there are all sorts of gotchas and surprises there.
Re: Kubernetes and back – Why I don't run distributed systems
#9I thought the DB isn’t supposed to go in the cluster?
Re: Kubernetes and back – Why I don't run distributed systems
#10> “JUST PUT IT ON A SERVER!!1”
For all your data: yes. It means persistent filesystems and databases.
Kubernetes will still be perfect to manage your running apps, but data is "the rest of the owl" of most devops / cd proponents and tools. "I should be able to rollback to a previous working state", well I hope your last deployment did not change your database schema.