Re:A story about a Kubernetes migration
by eeZah7Ux on Tuesday October 02, 2018 @10:30AM
(#18122037)
"Now we have a distributed monolith that requires 2x less developers to build and 5x more system engineers to deploy"
Re:A story about a Kubernetes migration
by falcolas on Tuesday October 02, 2018 @11:40AM
(#18122686)
Well, to be fair, all of those developers probably found themselves filling a systems engineer role "because the product developers are best equipped to handle the running and support of their own applications".
Even their documentation can't keep up. And with a release cycle of 3 months, and a deprecation cycle of 6 months, you need a team dedicated to keeping up with K8s state-of-the-art; so much of that knowledge you picked up a year ago is at best stale, and at worst wrong.
Sure, it makes setting up and keeping a set of containers up simple. But that's never really been that hard.
To paraphrase an article from a few weeks ago:
"We made microservices to address the problems with monoliths."
"We made containers to address the problems with microservices."
"We made Kubernetes to address the problems with containers."