@jacques42

00:31 🔄 Big Bang Deployment involves pushing all changes at once, causing short downtime; careful preparation and testing are crucial, with rollback as an option.
01:34 🏃‍♂️ Rolling Deployment updates different server parts incrementally, preventing downtime and allowing early issue detection; however, it's slower and lacks targeted rollouts.
03:32 🔄🔵 Blue-Green Deployment uses two identical environments; one serves live version while the other tests new version; seamless transitions and rollbacks, but resource-intensive.
05:59 🐦 Canary Deployment tests new version on a small subset (canaries) before full-scale rollout, offering safety net, control, and targeted rollouts; requires careful monitoring.
07:57 🎚️ Feature Toggle manages specific new features within an application; allows turning features on or off for certain users, offering control, A/B testing, but needs careful management.

@prashantkaddam

On small input on the video when ever you are explaining one strategy the name of the same strategy should be visible above diagram so that if at all some one jump the video still feels connected with what ever is visible on screen

@godwineffiong5164

I wish I can like this video more than once. The use of diagrams makes the understanding so much easy. Thanks a lot

@cesarp6761

Your videos are supreme!! Well done, to the point.. just perfect.. one way to make it better.. as you always talk about different topics.. for example here.. 5 deployment strategies.. put. In the lower left portion of the presentation the current strategy you are talking about.. and so for each topic you cover.. so that everybody know what item you are currently talking about. Cheers!

@KuopassaTv

I just upload files, works fine half the time

@cassianocominetti7784

Best video on deployment strategies! Thank you!!!

@BornaLoncaric3

By far the best video explaining the deployment strategies clearly, presenting them well visually and straight to the point explanations. Thank you!

@dineshnagumothu5792

From my experience, don't lure yourself into feature toggles unless its minute change like show/hide a button. They will become increasingly complex to test and later when you remove those toggles you need to test again anyway

@willzou641

nice video. I worked in different companies and met all of these deployment strategies. Good for me to have a theory summary.

@dannyhd8301

The information graphics he uses are superb , the contents straight up PRO

@jimmyexx

Thank you for this video ! very helpful explanation!
We use rolling upgrade + canary deployment strategy.

@Martinit0

Probably worth noting that each feature on/off toggle doubles the test requirement (if you need to test all combinations of features). So that explodes really quickly if toggles are not removed relatively quickly.

@MAtukulis

A combination of rolling deployment, canary deployment and feature toggles with good database design practices allow to maintain high service availability. Great video!

@bigbyte-fp

A nice demostration, very cleand and understandable, it would be heplful if the slides had the name of strategy being shown. Thank you very much for your work.

@Man-lg7vm

i use vercel. Thank you

@jenroot7875

How are databases changes handled with Rolling Deployment?

@vcfirefox

We used feature toggles. I thought it was a messy way to manage features until I saw this video. It's a deployment strategy! Wow

@vasanthbloginfo

We are using a blue green deployment model for our bigdata project in prod

@DianaDelibaltov

How about shadow deployment? While serving the current version to the user, you also do an async call to the "new" system. The new system does its computation but does not send it back to the user. The new system logs what "would have happened", which is used in analysis. Depending on the analysis results you can move on to canary, or rolling deployment, etc.

@ultimateagg

Super helpful video. How you creating such unique diagrams and animations?