4 ms·
I'll take the devil's advocate: * All these new tools, they give us options, no? Use the right tool for the job, the ability to switch if something becomes old
by brodouevencode 4y ago
I'll take the devil's advocate:
* All these new tools, they give us options, no? Use the right tool for the job, the ability to switch if something becomes old/unmaintained.
* Is this actual complexity or perceived complexity given your experience? The node ecosystem looked very complex for me (someone coming from Python) until I actually got into it. Now it seems pretty run-of-the-mill.
* Is k8s really all that hard? Build a container and you don't have to worry about provisioning it and deploying it again.
There may be good reasons to use some of the technologies you pointed out. And that's a strong may because I can easily come up with arguments in the other direction in addition to yours. I say all this to mean you just shouldn't dismiss it because it seems hard. It may be and it may not be, and if it is it may still be worth your time if the payoff is great enough. There you have to do the legwork to figure that out.
- dolni 4y ago> Is k8s really all that hard? Build a container and you don't have to worry about provisioning it and deploying it again. No, the deployment of a container to Kubernetes isn't hard. And it better not be, that's supposed to be the advantage. What's hard is literally everything else about it. And that may be a fine tradeoff if you are at the scale to need it and have a team to manage it. But there are many organizations where that tradeoff does not make sense.
- brodouevencode 4y ago> What's hard is literally everything else about it. Absolutely. To me it only makes sense in large orgs that can dedicate resources to managing the platform. But I did bring it up because I, as the user of such a platform, don't have to worry about writing CloudFormation or Terraform because the infrastructure is provided to me. But yes, it's tough otherwise.