search

pulumi / pulumi-hugo

A Hugo module containing content and layouts used on pulumi.com, including hand-authored docs, the Pulumi blog, and Learn Pulumi.
Apache License 2.0
32 stars 146 forks source link

Docs comparing Pulumi to CDK contain wrong information #926

Closed gshpychka closed 2 years ago

gshpychka commented 2 years ago

On the page comparing Pulumi to CDK, there's a bunch of wrong information about CDK being limited by YAML.

Here's a brief list:

Troposphere and CDK compile down to YAML and are therefore limited in what they can express.

This is not really true, YAML doesn't limit it.

The Pulumi engine understands general-purpose language patterns, dependencies between objects, and therefore delivers a better overall experience.

CDK does too. It understands language patterns, dependencies between objects, etc. It then compiles it down to JSON, accounting for all of these.

Pulumi also supports going beyond what you can express in YAML, such as building and publishing a Docker container image, authoring serverless functions in code, automating packaging and versioning of code, and so on.

CDK does too, it is not limited by YAML. You can build assets like docker images (https://docs.aws.amazon.com/cdk/api/latest/docs/@aws-cdk_aws-ecr-assets.DockerImageAsset.html), upload the resulting image to ECR, upload environment files to S3, or upload an arbitrary zip file to a bucket (https://docs.aws.amazon.com/cdk/api/latest/docs/@aws-cdk_aws-s3-deployment.BucketDeployment.html). You can also absolutely author a serverless function in code - CDK will build the image and upload it for you (e.g. https://docs.aws.amazon.com/cdk/api/latest/docs/@aws-cdk_aws-lambda.Code.html#static-fromwbrdockerwbrbuildpath-options).

You can also write your own Custom Resources that run arbitrary code and are not limited by YAML or even CloudFormation.

The impression that I got when reading this is that it was written by somebody who has never used CDK, so it left a bit of a bad taste.

susanev commented 2 years ago

@gshpychka thank you for opening an issue and calling out some specific areas where we need to improve! We, unfortunately, haven't been able to update this page since it was written a few years ago. Some folks are working on updating all of our compare to pages in the new year so you should see some improvements there soon.

gshpychka commented 2 years ago

@susanev that's good to hear. I really hope you consult with people who have practical experience with the tools you're comparing to, so that the docs seem more genuine.

susanev commented 2 years ago

@gshpychka apologies for the delay! last night we shipped changes to both of these pages. pls take a look and let us know if this addresses your feedback. thank you!

cnunciato commented 2 years ago

Hi friends! As @susanev mentioned, we've shipped some updates to these docs, and they seem to address these points, so I'm going to close this issue for now. But if you feel like something still needs fixing, feel free to reopen with any details you like, and we'll get 'em looked into. Thanks again for the excellent feedback -- we really appreciate it.