I just upload files, works fine half the time

This guys infographics are thest BEST I have seen. It just makes it easier to follow/understand. Great videos.

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

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

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

Excellent. Hope to see a dark deploy video soon as well 🙏 if one doesn't already exist. Compliments to the chef, another high quality presentation that is clear and articulate 💯

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!

Best video on deployment strategies! Thank you!!!

Thanks - awesome video and excellent explanation.... the visuals together with the detailed explanation is just awesome! Thanks so very much.

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

Really insightful content, keep up the good work!

Another excellent video from ByteByte !

Very useful. Thanks so much for your work.

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.

I watched several videos and it was a great help to my interviews for Cyber Security. I hope that in the future you come up with something with Cyber Security. I will definitely purchase your books when I secure a Job in Cyber Security.

nice, simple and steady!

Thank you! Very useful!❤

We use big bang and it has worked reasonably well. The best for us would be blue-green, and then adding feature toggle. Blue green would also help isolate our engineering testing because right now our UAT environment is shared by many groups and there can be resource contention at times. The main reason we don't do blue green is cost. It would be extremely expensive to add a duplicate production environment.

Great video!

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

Great video. It sounds like no matter what strategy, it’s going to be complex and expensive, however.

Have been enjoying your slides whenever I take a look at them. Great slides and much greater topics!! Would be interested to know what you use to make them or how you do it. Do you have a video already. Another thing, what do you think if you added a sub-heading of which item you are discussing. It keeps the audience on track and not loose which item you are discussing. Keep it up!!!

I love the amazing animations, what software do you use to make the video?

This channel is knowledge treasure for people moving from average developer to pro. You should write book about all things you have here.

Excellent

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

We send an email to users to refresh their webpages everytime we deploy 💀

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

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.*

I have used feature toogle. Works best!!!

Great!

i use vercel. Thank you

We use a modified “blue / green” works well for our purposes !

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.

Thanks!

Uou can use in memory data bases as main database as well

In a smooth CI/CD setup, I find feature toggling via feature flags, the safest and easiest way to go. The smaller the feature, the better. He’s right though - if you’re not diligent about deleting old flags, code, tests, etc, your tech debt will pile up. Something teams generally need to work hard to prevent, regardless.

you are life saver

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

I wish the video talked a little more about the complexities associated with having multiple versions of your application up at the same time; how new features and database migrations have to be implemented in a certain way to accommodate the deployment strategy...

Hello Guys. Thanks for this important video! Super Thanks. May I ask? What kind of software makes such smooth and beautiful slides?? Does any one know about this?? Thanks! Guy!!

What tools do you use to make such nice motion diagrams????

anyone knows what platform they use for the graphic support ? (animation and so, very clean)

wonderfull

“Toggle debt” - haha great term! Something I’ve certainly experienced.

We do Big Bang deployments where I work. It works fine as long as your changes are kept relatively small.

How are databases changes handled with Rolling Deployment?

You have missed a deployment where a parallel (usually smaller with a canary) env is running and we compare result from A and B. If both are giving same result on prod - we can proceed. It is more about testing of the canary. It also requires a system that allows pure code (any direct writes to any DB must be mitigated using some abstraction/mock).

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.

I don't deploy myself but my team used to use Big Bang strategy I guess. They start deploying at 1 A.M. hoping to finish until morning.

Copy files directly to servers, works fine every time !

This is top-notch in every aspect. I recently enjoyed a similar book, and it was top-notch. "Mastering AWS: A Software Engineers Guide" by Nathan Vale

So how do you do incremental if there are backend changes such as those in the database?

feature toggle strategy is very hectic. It is being used in my project, testing is other thing but with increase in number of toggles it becomes very very complex to keep track of feature changes

Such deployment videos never assume we have a Database at the backend :) Looks all possible without the Database, all seems difficult when DB comes into play.

What does AWS use? Serveless, EBS? Which model they use?

Make video on video editing

What if we use kubernetes ? By default the deployment of replicas are rolling, right?

with all these strategies, most of us will still deploy during Fridays lol Great video btw :)

How is it called if I only uploaded the main code to a Lambda serverless function?

We are deploying new release on different geographical area gradually.

Do your books contain a similar style or the same content?

YOLO!!!

I guess that I don't understand something. If I'm using the blue/green option and I move my user base to the new, green option, which they use for a week or two. They eventually start to find issues and want to role back. How do I move all of the updated / new information that is now on the green servers back to the blue servers. This can't be lost information and running scripts to find all of the updated information and transfer it back into the blue system doesn't seem possible. How would you cleanly Rollback?

so what's diff between rolling and canary?

If new version make change on databases, how to rollback in this case?

🎉🎉

does anyone curious about how to make a video like this? i mean the animations of system design images

Make video on Video editing like pro

It would help if you could do a 1 minute summery at the end.

problem is data integrity while deploying and migrating to the new version.

Rolling Deployment.

I'm not into devops so I don't think I will ever see this. Thanks though

Please, have in mind that Q&A != QA

It’s pretty hard to read the slides on a mobile phone

Canari deployment? More like guinea pig deployment 😅

it's a bit different, some sentences sound nice, but not reality.