4 ms·
What I find is missing from this discussion: the major advantage of config-based deployment is that it's relatively stateless and easily reproducible. Their pai
by o11c 3y ago
What I find is missing from this discussion: the major advantage of config-based deployment is that it's relatively stateless and easily reproducible. Their pain point tends to be when state leaks in.
A lot of traditional approaches are gratuitously stateful, and there's a lot of room for tooling improvement there even if you want to avoid YAML.
- randall 3y agocdk is so good for aws... i haven't used terriform but I'd bet it's just as good. Stateless infrastructure is amazing. Checking my infra into code is awesome.
- eptcyka 3y agoCould you elaborate on the state here?
- o11c 3y agoFor example, docker is notable for breaking people's networking and leaving it broken even if you later uninstall docker. Sometimes it's a mere mess instead of breakage. This isn't a docker-specific issue, docker is just what a lot of people use. Or literally anything to do with certificates/keys. GPG in particular is actively hostile toward stateless operation, far more than is necessary in an admittedly tricky field.
- ncrmro 3y agoKubernetes is declarative. There are now operators published by AWS and azure that you you define and provision managed cloud services like RDS and S3 a CRDs from a cluster.