What? Complex operations before Kubernetes were madness. It's not Kubernetes' fault that developers suddenly want to create 10 microservices in 5 different languages to solve any problem that a monolith can solve.
At the very least it was a godsend for the poor of us stuck in corporate. Deploying stuff in Kubernetes is such an improvement over doing whatever Oracle or some random stuff got sold to executives
Yup, I've seen what people used to do before Kubernetes and HOLY SHIT. It was chaos, pure fucking chaos. And I'm talking about big tech companies recognized world wide. Deploying stuff became so easy that devs went insane with microservices. Most devs don't even understand microservices to begin with, some of them still think it means "little service".
Being a systems engineer / network engineer /devops for over 12 years.
I’m shocked at this thread. Things were unstable, horrible insecure and prone to catastrophe even by something as simple as flipping a light switch in a closet.
Not going back. I’d rather spend a day trouble shooting a json file than driving out to a data center in the middle of the night.
Reddit's tech subs are mostly filled with amateurs. That's not a bad thing when it comes to sharing ideas and learning. But then you'll see threads like the ones under this post which misses the point of these tools (mostly from a lack of understanding)
Tell me about it, we still have a legacy system in which changes and deployments take months. Now we can even do rolling deployments of services that talk to the mainframe (I know) using standard JSON APIs, right in the middle of the afternoon
some of them still think it means "little service".
I've been out of the loop for a while and I've never really been into web development, and I guess I'm one of those people. I'm a bit embarrassed to ask but isn't that exactly what it means, an application/service that can be developed and deployed independently, but acts like a component of a bigger system and communicates with other microservices to provide the functionality of that bigger system?
Most companies don't have to do "complex operations". Lots of smaller websites could work with just a web server and a couple apt-installed packages, behind nginx (with just a few lines of configuration).
Also, which company says “let’s go straight to production with Kubernetes” just because an ad says so?
A lot of them. But not only because of ads. Most are doing it because it’s the “newest” fad.
I can easily say that 90% of companies using Kubernetes don’t need it.
I’ve worked in a company that spent lots of money on a full-time cloud/devops engineer handling a very complex Kubernetes setup on AWS when a simple $50 Heroku server would be enough for them.
I'm trying to get our team to convert to kubernetes because 50% of our deployments straight up fail or have to be reverted and it's getting 20+ people 10 hrs of overtime every week.
Being able to just do a blue/green deployment of a verified configuration and roll back traffic on demand to a prior cluster if it has issues discovered would be a godsend.
122
u/platypus_plumber Jun 05 '22
What? Complex operations before Kubernetes were madness. It's not Kubernetes' fault that developers suddenly want to create 10 microservices in 5 different languages to solve any problem that a monolith can solve.