“You don't need this overengineered goo for your project.”
1–10 of 107 posts
Re: “You don't need this overengineered goo for your project.”
#2recently facing the dilemma of choosing between k8s vs something more basic.
Features that seemed to be advocating for k8s were not server provisionning, but instead :
log management, easy setup of blue/green & canary deployment, not having to restart a vm upon new code deployment, etc...
How would you do those things as easily with other techs ?
Re: “You don't need this overengineered goo for your project.”
#3[deleted]
Re: “You don't need this overengineered goo for your project.”
#4Nomad ftw
Re: “You don't need this overengineered goo for your project.”
#5That’s not an architecture diagram though, so it doesn’t represent the complexity at all.
I’m sure a troubleshooting map for bare linux server wouldn’t be less complicated than that.
Re: “You don't need this overengineered goo for your project.”
#6That’s not an architecture diagram though, so it doesn’t represent the complexity at all. I’m sure a troubleshooting map for bare linux server wouldn’t be less complicated than that.
100% and one of the great things about k8s is that this diagram applies to essentially any application. Standardisation is awesome.
Re: “You don't need this overengineered goo for your project.”
#7This seems like something you can implement in a workflow tool like Netflix Conductor and we can automate the debugging process with visuals.
Re: “You don't need this overengineered goo for your project.”
#8[deleted]
Re: “You don't need this overengineered goo for your project.”
#9recently facing the dilemma of choosing between k8s vs something more basic. Features that seemed to be advocating for k8s were not server provisionning, but instead : log management, easy setup of blue/green & canary deployment, not having to restart a vm upon new code deployment, etc... How would you do those things as easily with other techs ?
It's all trade-offs. k8s is feature-rich, flexible and configurable but that also means high complexity. Simpler tools might not tick all the feature boxes.
As long as your applications follow 12-factor principles it shouldn't be too hard to move between different orchestration tools and you can pick the one that best suits your needs.
Re: “You don't need this overengineered goo for your project.”
#10I love these Twitter takes. They say something to get attention but if you look at it for more than a second it's.. it's just nothing data
Comparing a troubleshooting guide to running a site on a couple of servers is a bit too different for me. Compare it to a troubleshooting guide for those two servers, let's see how they stack up. No using any "ask {specific person}" either
Don't get me wrong, kubernetes is overkill for most side project level things. I don't disagree, I just like to see things knocked down a peg fairly!
Also as mentioned by this tweeter they use more than 2 servers anyway
https://twitter.com/shadowmanos/status/1434980544740306947
They could probably save on resources and maintenance effort if they switched to containers assuming this is still the same or more
> This is #1 in a very long series of posts on Stack Overflow’s architecture. Welcome.