Continuous Integration vs Continuous Delivery vs Continuous Deployment in a Easy Way
ฝัง
- เผยแพร่เมื่อ 19 มิ.ย. 2024
- Continuous Integration vs Continuous Delivery vs Continuous Deployment in a Easy Way
Agenda:
What is Continuous Integration
What is Continuous Deployment
What is Continuous Delivery
************************************************************
Continuous integration (CI) is a software engineering practice in which frequent, isolated changes are immediately tested and reported on when they are added to a larger codebase.
In continuous deployment, every change goes through an automated pipeline and a working version of the application is automatically pushed to production.
Continuous delivery helps you build a refined version of the software by continuously implementing fixes and feedback until finally, you decide to push it out to production. - วิทยาศาสตร์และเทคโนโลยี
well explained Akash
Thanks a lot Mukesh Sir 🙂
Best ever video about CI/CD
Satisfied with your explanation. Thank you 😊
Quite an amazing video, Thanks a ton Akash. Your answers to bharat is spot on!
very nice explanation. So basically organisations either they use C. Delivery( example: who can take down time for their production upgrade) or C. Deployment(FB,twitter who cannot take down time for production upgrade). Super. thank you once again.
Really you gave a lot of information in this 8 min video. Thank you Akash sir for sharing this.
Thank you I understood this.
Very simple, very informative, well explained thanks so much for sharing this with us.
Glad you enjoyed it!
Good Explanation
very well explained
Excellent explanation
Good explanation sir 👏❤️, one thing i wanted to add is that , please try to add more realtime examples so even beginners can understand easily.
Well explained
Well explained bro, I hope more videos on DevOps real time.
It was really good. Well curated content and easy explanation Akash. I'm glad you stuck to your first line till last: "I'm over confident but sure that you'll not forget this easily."
Kudos. Keep up the good work.
Thanks, Rishabh.
Well understood
Nice sir
very nicely explain.😇😇😇😇
Simple and Nice .. thanks Akash
Most welcome 😊
Awesome bro....go ahead
Thank you so much 😀
Good one 👌
Thanks ✌️
Nicely explained Akash.
Thanks a ton. Keep watching 🙂
Nice..❤️
Thanks 🤗
CAN WE MAKE OUR BRANCH READONLY in azure repo? IF YES how can u pls tell
Thank you so much brother for explaining in an easy way. I have few things to ask buddy...could please look into them:
1. Does companies choose either Continuous Deployment or Delivery based on product/app usage by their customers/clients? Does these practices have impact on the cost?
2. Can you please help me with an example, why can't all companies use Continuous Deployment? Is it up to the company or to cut-down the cost or again based on their product usage(high/low)?
I understood why companies like Amazon or Facebook can't even think of Continuous Delivery. Since their app usage is more all over the world.
I grabbed a lot of knowledge in this 8 minutes video, how exactly the flow is happening. Thanks a lot.
I am glad that you liked the video. That's a very good question Bharath and really appreciate your effort towards understating the topic and providing me the feedback.
Both Continuous Delivery and Deployment are being used as the best practices and we cant debate on which is right and which is wrong.
Giant ERP companies can't take risk of making downtime in their application and hence if they want their release to be more stable, reliable, and controllable then they go for Continuous Delivery and also they have a planned schedule for every new feature update. They also ensure releases are completed in smaller chunks so that they can deliver it smoothly to customers without downtime and failures.
One liner for Continuous Deployment: Its an extension of Continuous Delivery. Continuous Deployment should be used by the organizations where they have all the services as part of the Blue-Green Deployment model which is widely being used in DevOps. If there is anything wrong in the automated deployment pipeline the application should still be accessible to customers using the secondary routes or services. Please check the below video if you want to know more about Blue Green Deployment in the Continuous Deployment pipeline.
Blue Green Deployment Model:
th-cam.com/video/rZTW3p1p1e8/w-d-xo.html
@@TechShareChannel Thanks a lot brother for the detailed explanation. Will look into the model. You cleared all my confusion n doubts by explaining things in simple language. I was able to find this because of Mukesh bro post in facebook. Will follow your videos closely from now on. Thanks a ton for sharing buddy
👌👌👌👌👌
Quite good and easy understanding video....but I am in dillemma actually,since I am currently working as a developer with experience of 2 yrs but does not have much exposure in developement part as project was already completed only maintainence and little changes was done so I tried switching for Front end developer but not able to clear interviews but I got an opportunity for Implementation engineer role for Continous Delivery in product based company ,so is that will be a good option for me ? since there is less opening in Implementation engineer right ? and will that be a part of devops later for me ? and will that provide me good future ahead ? Please help.
Hi Gurpreet. Let's discuss this in detail. Can you please send me an email.
@@TechShareChannel Yeah sure sir, my email is gsinghbhupal@gmail.com
Continuous Delivery --------> Pubg closes its server (under maintenance) for upgrade
Continuous Deployment ---------->Amazon service which works all around the hour
please correct me if i am wrong
You are right ✅
The introduction is obnoxious
Thank you 😃 Will try to improve going forward !!