3 ms·
I'm currently using tools like CDK and Pulumi, which allow to abstract multiple resources neatly into one component. Do you think monolitic Lambdas still make
by k__ 5y ago
I'm currently using tools like CDK and Pulumi, which allow to abstract multiple resources neatly into one component.
Do you think monolitic Lambdas still make sense in that case?
- giorgioz 5y agoWe 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-with-aws-cdk-1788ab4d1d27 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.
- jayair 5y agoIf you are using CDK then check out SST: https://github.com/serverless-stack/serverless-stack 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-functions-with-visual-studio-code.html https://serverless-stack.com/examples/how-to-debug-lambda-fu...
- qvrjuec 5y agoCDK(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'.