How Big Tech Ships Code to Production
Vložit
- čas přidán 8. 11. 2023
- Get a Free System Design PDF with 158 pages by subscribing to our weekly newsletter: bytebytego.ck.page/subscribe
Animation tools: Adobe Illustrator and After Effects.
Checkout our bestselling System Design Interview books:
Volume 1: amzn.to/3Ou7gkd
Volume 2: amzn.to/3HqGozy
The digital version of System Design Interview books: bit.ly/3mlDSk9
ABOUT US:
Covering topics and trends in large-scale system design, from the authors of the best-selling System Design Interview series.
Often times convincing that a issue is fixed takes more time than actually fixing it.
I'm an Agile project manager at a major financial institution, and it's incredible to witness our daily operations summarized in an impressive and efficient SDLC flow. Thank you!
Concise video with the required information for newbies in less than 5 minutes.
Quite close to what we do, just a small change, instead of deploying main/master to production, we create Release Branch with a cutoff of 1 week before rollout for UAT, stress testing and Marketing SignOff, then deploy that package.
every single word you said is gold!!! nothing extra said nothing missed out
We automate our unit testing on PUSHes. So that PR only happens on tested code. We have automated functional tests and fuzzing on pre-prod code, before pushing to production. Good video!
Great explanation!👏🏼👏🏼👏🏼
Thanks Sahn 🎉
I learned so many concepts from you
Thanks Sir
You are great explained very clear
This is an excellent video to show AI-Advocates the real complexity of the software industry, especially as an answer to the new mainstream phrase "IA will replace developers".
You are doing great work sahn lam.
Most of the seniors in the IT field are not aware of this.
That's great, we are applying that as well.
Nice video, well explained!
Nice work!!!
thanks now i can change the color of button for our production site. thanks
Thank you
well explained!
Awesome video!
Wanted to ask if you could make a video or newsletter issue about how a RFC / Design Document gets created and is used? Would really love to see how Big Tech works through this specific part of the process!
thank you!
Wondering if it is a typo in Release Step the environment labeled as "Development Environment" which is supposed to be "Production Environment"?
In our case, merge to the main branch is only done after all the testing is done and all the tasks run on the PR branch first, only then it gets merged to the main branch, otherwise everything seems very familiar ✌😊
You have a staging environment for each branch? Or do you mean you have a ci pipeline?
Same here, only merged to master when fully tested in QA env.
@@sourandbitter3062In my case we use a CI pipeline with multiple instances. QA1, QA2, QA3 and so on.
The QA Analyst pushes the branch to one of the nodes and test it isolated.
Is the main branch pushed to ci/cd pipeline? Do env variables reside in main?
Title is changed 👍
How do we draw such maps ? What software do we use ?
Great video, though at the bottom shouldn’t that say “Production environment” rather than “Dev environment”?
Should we merge to main branch before QA testing is done ? Also, do big tech companies follow a release cycle ? Also there should be multiple deployable environments in dev if they are following a release cycle
There is no single way or solution. Every company and sometimes even teams within a company do it their own way. Some follow release cycles, some ship code continuously. Some have development/testing/integration/preprod environments, while others might only have a testing environment for QA to check end to end functionality. There are different approaches to maintaining your git repos as well, he described a trunk based development, where everything gets merged into master(trunk). Some people might still follow git flow with its merging hells.
Cool video
That's nice, but can you make the logo bigger?
I miss those long in depth videos..
Don't use feature branches, use small self-contained incremental stories which can be tested and delivered using CI approach. This is more agile and gives early feedback and reduces chances of merge conflicts.
I don't see how those techniques are exclusive?
Don't use feature branches if your solution is trivial.
We tried both approaches on a large scale project and found feature branches cause more problems then small increments. When trunk is evolving fast it's hard to keep branches in sync and merge.
@@nigh7swimming Above, you say "don't do this". Then you say you tried and "it didn't work for you".
I don't see how you get from it didn't work for us to nobody should do it. Maybe there is even a skill issue involved.
@@user-dq7vo6dy7g it didn't work for us, a big American corporation full of pros. But sure you know better, suit yourself. We tried and it didn't work is what I'm saying.
What tools you use for presentation and animations? Anyone have idea?
I want to know this too
It’s in the description
@@zeektm1762 thanks. I didnt notice that.
whats this "testing" you talk of? :p
Overrated bs i guess 🤪
Funnily enough i knew one company that didn't do any sort of 'staging'. Code was directly deployed into prod.no CICD even configured. Literally uploading code to prod hosts. Insanity
Jenkins .... urggghh