Re:Anti-Patterns to Avoid in Lambda Based Apps
by qvrjuec on Friday November 05, 2021 @11:18AM
(#29120486)
CDK(and infra as code in general) is amazing, especially for use cases like this where one would be responsible for deploying and creating resources around 10s of lambdas for one 'service'.
Re:Anti-Patterns to Avoid in Lambda Based Apps
by giorgioz on Friday November 05, 2021 @10:58AM
(#29120194)
We are using AWS CDK too! CDK is freaking AWESOME to write Infrastructure as Code.
AWS CDK
https://anjith-p.medium.com/writing-infrastructure-as-code-w...
Yes in my opinion the right division is
GOOD 1 lambda = 1 service
BAD 1 lambda = 1 endpoint
I'm eager to chat with you about CDK since it's kind of new and I don't know anyone else using it. Feel free to write me at giorgio DOT zamparelli AT gmail DOT com to chat about CDK, Lambda, serverless, Infrastructure as Code.
Re:Anti-Patterns to Avoid in Lambda Based Apps
by jayair on Friday November 05, 2021 @12:54PM
(#29121861)
If you are using CDK then check out SST: https://github.com/serverless-stack/serverless-stack
It's based on CDK and has a great local development environment for Lambda. It allows you to set breakpoints and test it locally: https://serverless-stack.com/examples/how-to-debug-lambda-fu...
Do you think monolitic Lambdas still make sense in that case?