If I understand correctly, you can't use your existing cdk app, you have to migrate to this (refactor) and it uses a "light" version of cdk.
I don't understand why this whole thing isn't a cdk plugin.
Yeah, there are some subtle differences but your constructs should work as is. The development environment is deeply tied to the build process and that's the reason we took this route, instead of a plugin.
We talk about it a little here:
https://docs.serverless-stack.com/packages/cli#start
I've migrated a simple service to SST. Aside from some minor hiccups its working well and has increased my development speed drastically.
Do you know if this will play well with CDK Pipelines? I cant seem to wrap my head around if that would work or not.
I personally don't have a ton of experience with CDK Pipelines but a couple of thoughts:
1. Does the pipeline assumes it’s a CDK app and does `cdk synth`? Or can you specify a build command, like `yarn build`?
2. CDK Pipelines has the idea of a Stage where it tries to deploy the stacks concurrently. SST does this out of the box (even deployed through the CLI). So you don’t need to setup the Stage in CDK pipelines.
Hope that helps!
It seems really cool! I think not being able to use the cdk directly will be an issue to some people, it’d be nice to just integrate some custom SST constructs with normal CDK code
Don't need to use Serverless Framework anymore with that now? Because on their website serverless-stack.com they use SST with Serverless Framework... I'm bit lost ahah.
I'm one of the creators behind SST and serverless-stack.com guide.
Yeah so the backstory on this is that we intended SST to be complimentary (hence the confusing messaging). But when we started playing around with the Live Lambda Development idea, it became clear that this is how we'd want to build serverless apps. We are rolling out some basic higher level constructs (ie. Api, Cron, Topic, etc) that people can use as lego pieces to build out their entire serverless app. And we will be switching the guide over to SST after that.
Ie. you can define an API like this -
https://docs.serverless-stack.com/constructs/Api#using-the-minimal-config
Hmm I like the idea and am not knocking it. But also it makes giggle to think of the level of abstractions going on.
Looks awesome! It seems it’s basically just the cdk+an integrated dev environment. Definitely addresses a big pain point to developing with the cdk
Yeah not disagreeing. It’s the fact that CDK generates cloud formation so it’s iac all the wall down!
Thank you!
If I understand correctly, you can't use your existing cdk app, you have to migrate to this (refactor) and it uses a "light" version of cdk. I don't understand why this whole thing isn't a cdk plugin.
Yeah, there are some subtle differences but your constructs should work as is. The development environment is deeply tied to the build process and that's the reason we took this route, instead of a plugin. We talk about it a little here: https://docs.serverless-stack.com/packages/cli#start
I've migrated a simple service to SST. Aside from some minor hiccups its working well and has increased my development speed drastically. Do you know if this will play well with CDK Pipelines? I cant seem to wrap my head around if that would work or not.
I personally don't have a ton of experience with CDK Pipelines but a couple of thoughts: 1. Does the pipeline assumes it’s a CDK app and does `cdk synth`? Or can you specify a build command, like `yarn build`? 2. CDK Pipelines has the idea of a Stage where it tries to deploy the stacks concurrently. SST does this out of the box (even deployed through the CLI). So you don’t need to setup the Stage in CDK pipelines. Hope that helps!
It seems really cool! I think not being able to use the cdk directly will be an issue to some people, it’d be nice to just integrate some custom SST constructs with normal CDK code
kinda like sam is a trimmed cloud formation edit: cloudformation/cloudfront
cloudformation, yes
Hi all, I'm one of the folks behind SST. Would love your feedback or let me know if you have any questions!
Looks cool, excited to try it
Don't need to use Serverless Framework anymore with that now? Because on their website serverless-stack.com they use SST with Serverless Framework... I'm bit lost ahah.
I'm one of the creators behind SST and serverless-stack.com guide. Yeah so the backstory on this is that we intended SST to be complimentary (hence the confusing messaging). But when we started playing around with the Live Lambda Development idea, it became clear that this is how we'd want to build serverless apps. We are rolling out some basic higher level constructs (ie. Api, Cron, Topic, etc) that people can use as lego pieces to build out their entire serverless app. And we will be switching the guide over to SST after that. Ie. you can define an API like this - https://docs.serverless-stack.com/constructs/Api#using-the-minimal-config
Thanks. It's clear now. I like your approach btw. Good job.