Hi, thanks for this video. What is the benefit of this way over referencing to SSM parameters via Lambda environment variables? Lambda would resolve the actual values from SSM parameters and you don't need to use any additional code. One benefit I can think of is that it can dynamically sense App Config changes without Lambda redeployment. But it's questionable advantage considering the amount of aditional configuration and code required to make it work this way.
You make incredible and useful content and I generally learn a lot from your videos. I just wish that you didn’t scream so loud at the beginning of each one… or just just give a second or two at the beginning at the video so that people like me have a chance to skip it. Please 😞
Hi Marcia! Thanks for the good explanation. At ua-cam.com/video/sq2HcRMLaLU/v-deo.html you have changed both language and boolean, but after you refreshed the request the language feature was changed in prior of boolean. Having such behavior we can't relay on changing all features at once right after redeployment. Is that correct?🤔
It would be so much more helpful if you used decent variable names representing a realistic example. For instance, the log level example you mentioned is a very viable one. Why use meaningless examples with meaningless names when creating the actual flag, instead of using the log level example?
I’ve been tasked with figuring out which feature flag tool my team should use, and this video cleared up so much for me! Thank you so much!
This is the best explanation of the AWS Feature Flags that I've seen. Great work!
Thanks
Hi, thanks for this video. What is the benefit of this way over referencing to SSM parameters via Lambda environment variables? Lambda would resolve the actual values from SSM parameters and you don't need to use any additional code. One benefit I can think of is that it can dynamically sense App Config changes without Lambda redeployment. But it's questionable advantage considering the amount of aditional configuration and code required to make it work this way.
Serverless queen is back. Greetings from Helsinki
I never left :D
A video a week for the last 5 years :D
Thanks for the video!
It took almost 1000 ms to run a pretty small lambda, do you have some benchmark how lambda performance is affected? thanks!
You make incredible and useful content and I generally learn a lot from your videos. I just wish that you didn’t scream so loud at the beginning of each one… or just just give a second or two at the beginning at the video so that people like me have a chance to skip it. Please 😞
Working on it!
Awesome! Thank you for doing an amazing work.
Thanks for watching!
Thanks a lot = )
Hopefully they add support to lambda@edge soon
Hi Marcia! Thanks for the good explanation.
At ua-cam.com/video/sq2HcRMLaLU/v-deo.html you have changed both language and boolean, but after you refreshed the request the language feature was changed in prior of boolean. Having such behavior we can't relay on changing all features at once right after redeployment. Is that correct?🤔
Such interesting topic !
Thanks a lot :)
it "Explode" ❤ I study CS in Spanish and we also said the code explode"
Jajaja si el español es mi lengua materna 🤯
It would be so much more helpful if you used decent variable names representing a realistic example. For instance, the log level example you mentioned is a very viable one. Why use meaningless examples with meaningless names when creating the actual flag, instead of using the log level example?
Hit the like button the second the video starts 😅
That is the way :D. hahaha thanks
return await... is redundant