If you want to learn more, check out my AWS Certified Developer Associate 2020 course : links.datacumulus.com/aws-certified-dev-coupon or my AWS Certified SysOps Administrator Associate 2020 course : links.datacumulus.com/aws-certified-sysops-coupon
I am not able to find any video on the Lambda deployment strategy, I think it has different approaches, blue-green, etc. I am preparing for SAA from your course, Thanks for that too.
Hello Stephane! Now the blue/green deployment can be done inside the elastic beanstalk configuration under the name of "traffic splitting". You may want to update your video.
All at one - 가장 빠른 배포방법, 가동 중지 시간이 생김, 추가비용 없음 Rolling - 부분적인 교체, 추가 비용 없음, bucket 사이즈에 따라 다양한 배포시간 Rolling at additinonal batches - 추가 비용 발생, 일관된 성능 보장, 긴 배포시간, 프로덕션에 좋음 Immutable - 가동 중지 없음, 비용 2배, 프로덕션에 좋음 Blue / Green - 블루(기존), 그린(새로운것),
Regarding "Rolling with Additional Batches", in step 4, why doesn't the system terminate "v1" instances and just end up with 4 v2 instances? Instead, it updates the remaining 2 v1 instances and ends up having 6 v2 instances then it kills the extra 2 to match the desired amount.
I wonder if this may be an oversight of the tutorial and the way it actually happens. It would eliminate some steps to simply terminate the v1s after step 4, but perhaps you would want to keep them for some reason? Or it may be attempting to maintain the idea that all instances get updated in batches, and there is one additional batch used as a placeholder so that number of instances used is maintained. Either way, not super important in the grand scheme of things.
If you want to learn more, check out my AWS Certified Developer Associate 2020 course : links.datacumulus.com/aws-certified-dev-coupon or my AWS Certified SysOps Administrator Associate 2020 course : links.datacumulus.com/aws-certified-sysops-coupon
I am not able to find any video on the Lambda deployment strategy, I think it has different approaches, blue-green, etc. I am preparing for SAA from your course, Thanks for that too.
Great explanation!!
Hello Stephane!
Now the blue/green deployment can be done inside the elastic beanstalk configuration under the name of "traffic splitting". You may want to update your video.
Merci Stéphane, c'était super clair !
Nice explaining. It is better than AWS doc.
Nicely 👍
Explained
All at one - 가장 빠른 배포방법, 가동 중지 시간이 생김, 추가비용 없음
Rolling - 부분적인 교체, 추가 비용 없음, bucket 사이즈에 따라 다양한 배포시간
Rolling at additinonal batches - 추가 비용 발생, 일관된 성능 보장, 긴 배포시간, 프로덕션에 좋음
Immutable - 가동 중지 없음, 비용 2배, 프로덕션에 좋음
Blue / Green - 블루(기존), 그린(새로운것),
Regarding "Rolling with Additional Batches", in step 4, why doesn't the system terminate "v1" instances and just end up with 4 v2 instances? Instead, it updates the remaining 2 v1 instances and ends up having 6 v2 instances then it kills the extra 2 to match the desired amount.
I wonder if this may be an oversight of the tutorial and the way it actually happens. It would eliminate some steps to simply terminate the v1s after step 4, but perhaps you would want to keep them for some reason? Or it may be attempting to maintain the idea that all instances get updated in batches, and there is one additional batch used as a placeholder so that number of instances used is maintained. Either way, not super important in the grand scheme of things.