I heard some people say replacing CFN templates with a full-blown programming language is overkill and will only lead to maintenance problems in the future.
I found the CDK to be quite powerful. I mentioned my issues with authoring raw CloudFormation in the post and it did mitigate those issues for me.
I think the CDK would be a good fit for dev teams who don't have dedicated Ops engineers in their team. I have worked with clients with such teams (full stack JS engineers) and they often default to just using the AWS Console to provision infrastructure cos CloudFormation is a painful dev experience and they are more concerned with shipping product features. Being able to write a few lines of Node and reuse constructs between projects would make the infrastructure-as-code discipline stick for them IMO.
That said, in fully serverless architectures where infrastructure is much less complex (no VPCs, etc), the CloudFormation pains are generally much less and I will still probably just use the resources section of my serverless.yml file to define my resources.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
How was your experience with the CDK?
I heard some people say replacing CFN templates with a full-blown programming language is overkill and will only lead to maintenance problems in the future.
Didn't use it myself tho.
I found the CDK to be quite powerful. I mentioned my issues with authoring raw CloudFormation in the post and it did mitigate those issues for me.
I think the CDK would be a good fit for dev teams who don't have dedicated Ops engineers in their team. I have worked with clients with such teams (full stack JS engineers) and they often default to just using the AWS Console to provision infrastructure cos CloudFormation is a painful dev experience and they are more concerned with shipping product features. Being able to write a few lines of Node and reuse constructs between projects would make the infrastructure-as-code discipline stick for them IMO.
That said, in fully serverless architectures where infrastructure is much less complex (no VPCs, etc), the CloudFormation pains are generally much less and I will still probably just use the resources section of my serverless.yml file to define my resources.