AWS Cloud Development Kit (CDK) has become, in its short history, a very popular infrastructure-as-code tool. It’s not too surprising why - it allows engineers to use richer programming languages to define infrastructure, rather than having to use JSON or YAML. By Mike Roberts.
In this article author shares his thoughts - both positive and negative - about CDK, for technical decision makers. This should help as you make your own choices about what infrastructure tooling to use.
The article highlights the information on:
- The good
- Programming language superpowers
- Engineer enthusiasm The bad
- Runtime debugging headaches
- Ongoing meta-responsibilities
- The scary
- Longer-term operations requirements
- AWS support of CDK over the long term
- Should you use CDK or not?
Because of the fundamental nature of CDK being a client-side tool, and not a cloud-side tool, author thinks this expectation is false, or at least is yet to be proven. This brings up some the longer-term concerns outlined in the article. Nice one!
[Read More]