Serverless Stack

Hi, so I was looking at the SEED output and was wondering how I could break up my services into many services but still have dependencies to some common stack?

```
INFO: Checking for files changes in the ##### service...
0.07 s
Skipping the check since there is only one service in your app.```


Hey <@U0298UDNNGN>, with SST, most likely you just need 1 SST app in the repo. This feature was more useful for Serverless Framework projects where each service is a single CFN stack. And to deploy 5 stacks, u need to build 5 times. So having the ability to check which services have changed, and skipping them really speed things up.

Where as in SST, you can have multiple stacks in the same app. You only need to build once, and SST internally can figure out which stack can be skipped (no changes), and only deploy the changes stacks. So the “speed up” is built in.

that said, we are looking into updating lambda code directly if the CFN template hasn’t changed. that should speed up ur builds by quite a bit.