Тёмный

AWS Elastic BeanStalk Deployment Modes Introduction 

Stephane Maarek
Подписаться 110 тыс.
Просмотров 32 тыс.
50% 1

Наука

Опубликовано:

 

26 сен 2024

Поделиться:

Ссылка:

Скачать:

Готовим ссылку...

Добавить в:

Мой плейлист
Посмотреть позже
Комментарии : 10   
@StephaneMaarek
@StephaneMaarek 4 года назад
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
@nirajvisana
@nirajvisana 4 года назад
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.
@anesumugomba524
@anesumugomba524 Год назад
Great explanation!!
@aeroprojects
@aeroprojects 3 года назад
Merci Stéphane, c'était super clair !
@latest_news_stories
@latest_news_stories 3 года назад
Nicely 👍 Explained
@Ysonichero
@Ysonichero 2 года назад
Nice explaining. It is better than AWS doc.
@kimkihwan571
@kimkihwan571 3 года назад
All at one - 가장 빠른 배포방법, 가동 중지 시간이 생김, 추가비용 없음 Rolling - 부분적인 교체, 추가 비용 없음, bucket 사이즈에 따라 다양한 배포시간 Rolling at additinonal batches - 추가 비용 발생, 일관된 성능 보장, 긴 배포시간, 프로덕션에 좋음 Immutable - 가동 중지 없음, 비용 2배, 프로덕션에 좋음 Blue / Green - 블루(기존), 그린(새로운것),
@tugrulerturk8270
@tugrulerturk8270 4 года назад
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.
@SarpdorukTahmaz
@SarpdorukTahmaz 2 года назад
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.
@collynchristopherbrenner3245
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.
Далее
AWS Elastic BeanStalk Deployment Modes Tutorial
6:56
AWS Elastic Load Balancing Introduction
12:02
Просмотров 134 тыс.
Beatrise (пародия) Stromae - Alors on danse
00:44
Amazon EC2 Launch Types Introduction
7:47
Просмотров 3,7 тыс.
AWS Cloud Introduction
6:54
Просмотров 64 тыс.
AWS Lambda Introduction
9:52
Просмотров 22 тыс.
AWS Elastic Load Balancing Tutorial
7:47
Просмотров 65 тыс.
AWS Auto Scaling Groups Introduction
7:19
Просмотров 82 тыс.
Samsung копирует Apple?
0:36
Просмотров 842 тыс.