Regarding stacks… what is the best practice for cr...
# sst
a
Regarding stacks… what is the best practice for creation? Should I have 1 stack for each of my functions? or 1 stack for each of my services/apis?
g
I have the second one - 1 stack per service/api
multiple functions in each
t
I use one stack with organized modules that are called from it that represent multiple services
I don't there's a right answer, whatever feels manageable
I went with one because even though they're seperate services they still share some resources like vpc database etc
a
Makes sense.
I’m migrating from SLS.
And I have multiple SLS services, basically.
So I’m going to create 1 stack for each service.
f
@Adrián Mouly I’ve done a couple of restructuring… it’s been pretty easy to move ur Lambda, API routes, Topics around. At the moment, I keep all my Queues, Tables and Buckets in a “resources” stack since it’s trickier to move them around.