3 ms·
This makes a ton of sense. I can so totally relate to the emotional attachment to code you write vs stuff you buy. And also how yaml declarative stuff is a pain
by gingerlime 7y ago
This makes a ton of sense. I can so totally relate to the emotional attachment to code you write vs stuff you buy. And also how yaml declarative stuff is a pain compared to the relative joys of imperative code that does “your thing”, but it’s better to stick to it.
... but having started reading the good parts of AWS and also in parallel playing around with cloud66, I have to say, kubernetes (at least the wrapped-up cloud66 variation) felt compelling. And codeploy and IAM roles and all that sticky glue? Not really.
Am I falling into a trap?
- streetcat1 7y agoThe problem with the "clouds" is that there are two types of locks : code lock and data lock. The author only talk about code lock. Again, as Kubernetes mature it would become easier and easier to configure (think of it as unix/linux at its early days), and hence less and less code locked. However, Kubernetes does not have data lock. I.e. when you go to the public cloud, you are locked both in term of compute and in term of data. I.e. the egress prices are 10x.