What problems do you face with serverless on native CDK that are solved by this toolkit?
Serverless Framework has a great local developer experience for Lambda and API Gateway. It also has a great plugin ecosystem that covers most use cases. It makes it much easier to test and deploy your Serverless apps. CDK on the other hand only does the packaging and deployment. You can use it for one off Lambdas but I would not recommend building entire Serverless applications with it.
I'm assuming this is for manual deploys via cdk deploy?
You are right. But for folks that are using CI services like Circle, Travis and GH Actions, SST allows them to deploy concurrently without having to complicate their pipelines.
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.
Could you please elaborate on this?
What problems do you face with serverless on native CDK that are solved by this toolkit? I'm struggling to understand what the value add is.
I'm assuming this is for manual deploys via
cdk deploy? This can be avoided if you're using CodePipeline, especially via the new CDK pipelines module.Hi Simon,
Serverless Framework has a great local developer experience for Lambda and API Gateway. It also has a great plugin ecosystem that covers most use cases. It makes it much easier to test and deploy your Serverless apps. CDK on the other hand only does the packaging and deployment. You can use it for one off Lambdas but I would not recommend building entire Serverless applications with it.
You are right. But for folks that are using CI services like Circle, Travis and GH Actions, SST allows them to deploy concurrently without having to complicate their pipelines.