Re:Four years after its release, Kubernetes has come a long way
by meddlepal on Wednesday June 06, 2018 @04:54PM
(#17251033)
I strongly disagree. I've built a couple in house PaaS type systems in the past with various degrees of success on more classical tech like straight up EC2 using a variety of Terraform/Ansible/CloudFormation/Scripting but the dev experience has always been painful compared to Kubernetes.
Developers really love working with Kubernetes. It doesn't take a lot to get started and if you're not doing anything too crazy it is a huge productivity boon IMO.
Where things get hairy is persistence, but that's the case regardless of Kubernetes or not.
Re:Four years after its release, Kubernetes has come a long way
by auslander on Thursday June 07, 2018 @12:21AM
(#17253265)
>Terraform/Ansible/CloudFormation/Script
This number of tools speaks for itself. Yeah, you would be better off with out of the box stuff due to lack of skills.
Re:Four years after its release, Kubernetes has come a long way
by meddlepal on Thursday June 07, 2018 @07:39AM
(#17254914)
Ah yes, you're right. I am sure you have a much better understanding of the requirements each of these build outs sitting behind your keyboard over there.
Re:Four years after its release, Kubernetes has come a long way
by rvanmil on Wednesday June 06, 2018 @04:55PM
(#17251039)
Heroku is still amazing indeed. Our team recently moved all Node.js based systems from AWS to Heroku and it has given us a tremendous productivity gain and reduction in complexity. Before we made that decision we spent about 8 months experimenting with K8s, only to discover it actually made things way more complex for us and reducing productivity without any clear benefits.
I guess the popular term is "cargo culting". Or maybe Heroku is not hip anymore although it probably is the best advice for many companies.