How do services work in context with sst apps, wha...
# seed
a
How do services work in context with sst apps, what would be the pros and cons of dividing an sst app into multiple services as opposed to multiple stacks and finally should I be splitting my sst app into multiple services to create a truly asynchronous CI / CD workflow as compared to giant monolith?
f
Hey @Ashishkumar Pandey, it is recommended to have 1 SST app. The services concept on Seed was more designed for Serverless Framework projects.
Each Serverless Framework service is a single CFN stack, and often ppl have a handful of services. And being able to manage the services on SEED, and coordinate the deployment order had been helpful.
We took that learning and baked that into SST. You can have multiple stacks in a single SST app, and we automatically figure out the deployment order based on inter-stack dependency. And independent stacks are deployed concurrently.
So yeah, most ppl should only have 1 SST app in the repo, hence 1 SST service in a SEED app.
^ we have plans to revamp SEED’s UI to have it cater more towards SST apps.
a
Understood. Thank you.