Hi, I just rewatched the video showing the Live La...
# general
r
Hi, I just rewatched the video showing the Live Lambda development, and it seems like the thing works similar to having it, so we deploy on change right ? -> on save (locally, it will deploy the version of the lambda to remote (aws)) so if two people are working on the same lambda, they would be overriding each other’s work correct ?!
a
Incorrect.
Each developer would have their own stage.
So each developer would have their own lambda instance.
jamie-myCoolLambda
rob-myCoolLambda
..etc
This is easy to do, due SST requests developers to configure their own stage at the beginning.
r
ahhhh
very nice, thank you !
😉
a
👏
r
but that’s for api gateway related stuff
a
No, for all.
r
let’s say for instance that my issue is events related (eventBridge)
a
Every resource would have a copy for each developer.
r
ah okay,
a
You are going to have 1 EB for each developer.
1 function for each developer, 1 gw for each developer.
r
oh my
a
In my company we have….
<http://youfa.dev.yabble.com|youfa.dev.yabble.com>
<http://adrian.dev.yabble.com|adrian.dev.yabble.com>
and so on.. we have 4 backend developers, then we have 4 environments + dev + stage + prod.
r
hmmm
a
Each developer have their own stack/stage/resources.
Then, each PullRequest it’s also deployed on their own.
r
and that doesn’t get expensive ?
a
Why? it’s serverless, you pay for usage.
Not for amount of resources.
r
4 environments + dev + stage + prod. what would be the difference between dev and stage in your setup ?
Why? it’s serverless, you pay for usage.
that’s true
a
dev -> where we test the integration for each pull-request stage -> more stable, where QA tests production -> what customers uses
r
omg 🤯
a
With current setup I have 8 environments at the moment.
r
hmm
7 ?
or 8 because of you?
a
1 for developer1, one for developer2 (these running local) 4 PRs which are open, awaiting review 1 dev 1 stage 1 prod
And some other developers are working too, might create an environment right now 🙂
r
ahhh
got it,
a
Today is this, maybe tomorrow it’s just 3.
Hahaha.
3 envs are stable, the other ones are disposable.
r
1 for developer1, one for developer2 (these running local) didn’t get that part (the running local_
a
You can read about this development flow in the SST site.
Like we said before, SST runs partially local and partially cloud.
So those developers are running something locally.
And also something in the cloud.
r
what would be the local ?
I better read the material 😅
a
The lambda.
Lambda runs locally, and connects with WS to the cloud.
r
hmmm
a little difficult to wrap my head on what you are saying hehe
a
Just check the docs, this is explained there.
Yeah check in the doc, there is a diagram.
r
awesome, thanks Adrian
a
😉
f
Thanks @Adrián Mouly for your insights!
@Renan Cidale Feel free to bring it up if any part of the doc isn’t clear to you.
r
no worries, I just didn’t read “any” of the docs. but so far so good 🙂