Hacker News Reader

Comment by snypox | Hacker News Reader

Since I got to know CDK[0], I prefer it over serverless. It's supported by AWS, too. It can deploy your lambda, or it an just generate a Cloudformation template - these 2 covers the most important features of serverless that our team uses.

[0]https://github.com/aws/aws-cdk/tree/v1.18.0/packages/%40aws-...

View on HN

I like Architect serverless - https://arc.codes. A .arc file is way less boilerplate than a serverless.yaml and it outputs full CloudFormation. Also has awesome async middleware (heads up I wrote the awesome async middleware).

And now we have azure arc...

I've used Up [1] before but this looks even better. Thank you for the recommendation!

[1] https://apex.sh/up

Cool fact: this was created by the creator of Express and Koa! https://github.com/tj

I found CDK to be exactly what I was looking for. I found myself using either CDK or Amplify (or both) for new serverless projects. It’s now really infrastructure as code, not infrastructure as yaml files.

Can you elaborate on why you prefer it?

I like CDK because: 1. it's type-checked (using your choice of language/compiler) 2. modularity is done using in-app code, rather than extending serverless with plugins in javascript 3. i think cdk scales better to projects composed of multiple stacks 4. it's somewhat testable

As the fellow commenter said: I mainly like the power of a programming language (loops, variables, organizing file and directory structure).

As long as it outputs cloudformation I want nothing to do with it.

You need to store state somehow - either Terraform or Cloudformation, you don’t have that many options. And CDK hides the Cloudformation layer from you.

Reply on news.ycombinator.com