hey folks! brand new to SST.. in fact, brand new to CDK too (I’ve been using Serverless Framework) I have a question about how to architect our stack(s). I made a new SST app called “coretest”.. and I noticed I can create multiple stacks within this. SST deploys these as

<stage>-coretest-<stack name>

. is this a best practice, to just have a single folder that contains all of our microservices? so basically the stacks would be

<stage>-<app name>-<stack name>

?

I would start off with a single stack that deploys all your services. Once you have that going then you can evaluate if it makes sense to have multiple stacks in your app or even multiple apps. It depends on the details of your application

we have very clear-cut separate parts: • “core” - the backbone that most other services depend on: Cognito, RDS, a few buckets, etc • “api” - REST & GraphQL API layer • “media-processor” - handles encoding audio & video files • “chargebee-webhook” - webhook to handle user billing/subscription changes/updates

Yeah that makes sense. One repo, one app, and a stack per service

it would simplify a lot of stuff for sure. right now these are all separate repos.. it’s kind of a headache to maintain

yeah I tend to start off with everything together and only start to add layers of separation when there's a clear need for it