How Top Tech Companies Develop and Deploy Code with CI / CD Pipelines
ฝัง
- เผยแพร่เมื่อ 6 มิ.ย. 2024
- Ever wonder how top tech companies like Amazon Develop and Deploy their applications using CI / CD pipelines? In this video, I walk you through the development process that Amazon/AWS engineers use create software systems and deploy them quickly using safe deployment practices. Learn about the Git approach, deployment waves, deployment methods, auto-rollback, alarms, and more.
Learn more about Amazon's Development / Deployment Methodology here: aws.amazon.com/builders-libra...
Sign up for my Newsletter to receive regular AWS updates AND get a FREE PDF that includes 5 AWS Project Ideas: beabetterdev.com/aws-project-...
📚 My Courses 📚
AWS Learning Accelerator - Learn AWS Through a Hands On Project - courses.beabetterdev.com/cour...
AWS Step Functions Masterclass - courses.beabetterdev.com/cour...
AWS Lambda - A Practical Guide - www.udemy.com/course/aws-lamb...
🎉SUPPORT BE A BETTER DEV🎉
Become a Patron: / beabetterdev
📚 INCREDIBLE BOOKS TO BUILD YOUR ABILITY TO FOCUS AND ORGANIZE 📚
Deep Work - amzn.to/463oPRk
So Good They Can't Ignore You - amzn.to/3PPo48N
Digital Minimalism - amzn.to/3Q00nep
A World Without Email - amzn.to/3t6nGKq
Time Block Planner - amzn.to/44Z9nEI
📚 MY RECOMMENDED READING LIST FOR SOFTWARE DEVELOPERS📚
Clean Code - amzn.to/37T7xdP
Clean Architecture - amzn.to/3sCEGCe
Head First Design Patterns - amzn.to/37WXAMy
Domain Driven Design - amzn.to/3aWSW2W
Code Complete - amzn.to/3ksQDrB
The Pragmatic Programmer - amzn.to/3uH4kaQ
Algorithms - amzn.to/3syvyP5
Working Effectively with Legacy Code - amzn.to/3kvMza7
Refactoring - amzn.to/3r6FQ8U
🎙 MY RECORDING EQUIPMENT 🎙
Shure SM58 Microphone - amzn.to/3r5Hrf9
Behringer UM2 Audio Interface - amzn.to/2MuEllM
XLR Cable - amzn.to/3uGyZFx
Acoustic Sound Absorbing Foam Panels - amzn.to/3ktIrY6
Desk Microphone Mount - amzn.to/3qXMVIO
Logitech C920s Webcam - amzn.to/303zGu9
Fujilm XS10 Camera - amzn.to/3uGa30E
Fujifilm XF 35mm F2 Lens - amzn.to/3rentPe
Neewer 2 Piece Studio Lights - amzn.to/3uyoa8p
💻 MY DESKTOP EQUIPMENT 💻
Dell 34 inch Ultrawide Monitor - amzn.to/2NJwph6
Autonomous ErgoChair 2 - bit.ly/2YzomEm
Autonomous SmartDesk 2 Standing Desk - bit.ly/2YzomEm
MX Master 3 Productivity Mouse - amzn.to/3aYwKVZ
Das Keyboard Prime 13 MX Brown Mechanical- amzn.to/3uH6VBF
Veikk A15 Drawing Tablet - amzn.to/3uBRWsN
🌎 Find me here:
Twitter - / beabetterdevv
Instagram - / beabetterdevv
Patreon - Donations help fund additional content - / beabetterdev
#aws
#cicd
Usually wave1 is a small region and wave2 is the biggest region us-east-1, because you don't want to get to wave7 and only then discover the problem and rollback all the waves. If there is an issue you will most likely discover it in the biggest region. Everything that could go wrong will go wrong in us-east-1. The earlier you detect the problem the easier it is to rollback. The cost of the rollback increases the further your deployment progresses from wave1.
Great video. Thanks Daniel!
I would love to hear about the pace/cadence at which each iteration happens. For example for simple thing like CTA button background-color change. What is the time frame in which this thing get's into production and what is the developer workflow when his CL's are hanging for the review or CI. Does he waits? Does he take the next ticket? How fast is the CI/CD to see your change running in dev env? I mean... in simplest case... local WebPack gives you almost instant feedback. How "instant" it is at scale and workflow of AWS and the likes?
Great thanks!
I like your presentation, to the point and with illustrations, makes it easy to follow.
I wonder what tool are using for drawing, is this a tablet you mentioned?
14:50 question related to 1 Box Canary Deployment Strategy:
Is it possible to route a specific user to that ~10% where the new feature is released in production, so the QA manual testers can validate the new feature?
Thanks for sharing! Shouldn’t the arrow when 1 box rolls back not point to gamma, but rather from fleet to 1-box since its rolling back to what the fleet has running, not to what gamma has?
Excellent video. Thanks. I have my CodeCommit repository but my code is not in a repo yet. My code is sitting in Lambda functions and Glue ETL functions etc. Do you have a recommended video for getting code into a CodeCommit Repo and start building my CI/CD pipeline?
Excellent video Daniel!..I would like ask you two quick questions: 1. In the scenario where all are released on the fleet in right way then what happen with the instances called Ibox, them continuing running or them are detroyed? 2. This presented approach is an available concept only for AWS environments or could be apply for others env?
Thanks for sharing the Amazon practices. I'm wondering how long is a single deploy (to a single region and worldwide)? are deploys sequenced? i.e. would you have to wait half a day because 3 other people got to merge their changes ahead of you and so you must wait for your turn to deploy?
Basically our teams have scheduled deployment, and they need to be approved. Sometimes there are changes that are not allowed to be deployed on prod and that is handle by feature flags. In one deployment process probably there multiple changes that people from the team were working at and are accumulated in Gamma.
wonder if there is any project refrencing this pipeline or have to make one
Just fyi, I work at amazon as well and we don’t really do the commit squashing thing. That’s probably a per-org thing.
That's bad. Do squash your commits 😄
In my team we squashed our commits. I think it is a great opportunity to divide your task from boards. And then work locally.