Anupam

Day 7: Zero-Downtime Deployment Patterns. Interviewers give you a constraint: "10M users, can't have downtime." Then they watch your thought process. 4 patterns — know when to use each: >> Blue-Green → Full duplicate environment. Instant cutover. → Cost: 2x infrastructure → Use: stateless services, regulated environments >> Canary → Route 5% of traffic to new version first → Use: high-risk changes, A/B testing infra >> Rolling → Replace pods/instances gradually → Use: k8s default, low-complexity services >> Feature Flags → Deploy code, toggle behavior in config → Use: separate deploy from release (most powerful pattern) Interview signal: mention the database migration problem. Schema changes break all 4 patterns if not handled (expand/contract pattern).

@CheniBalasaiva1 That's a good approach

@Anupam_Devops In team environment better we can use Git merge instead of Git rebase. As it maintain the commits as audit history. Where as Git rebase, it re writes the commit.

git rebase vs git merge — when would you choose rebase in a team environment, and what's the golden rule?

Monday Motivation for all.

Monday Motivation for all.

Ever wondered what actually happens when you hit “Forgot Password?”

Ever wondered what actually happens when you hit “Forgot Password?”

Ever wondered what actually happens when you hit “Forgot Password?”

Ever wondered what actually happens when you hit “Forgot Password?” Credits: Mohamad Al Sayed

Monday Motivation for all. Yiprum’s law of action works for those who show up everyday.

Most people learn Jenkins like this: “Here’s how you write a pipeline” But interviews go like this: 🔥 “Production is down after deployment” 🔥 “CI is failing but local works” 🔥 “Artifacts not downloading” No step-by-step guide. Just chaos. I’ve listed 30 CI/CD scenarios that prepare you for that reality: • Debugging pipelines • Fixing deployments • Handling secrets • Optimizing performance Because DevOps ≠ writing pipelines DevOps = fixing them under pressure.

A container keeps restarting with exit code 137. What does that mean and how do you debug it?

Day 19/20 — DevOps Learning Series Learning tools is good. Building real projects is where the real learning happens. Today's video walks through a practical DevOps project: • CI/CD pipeline setup • Docker integration • Kubernetes deployment Perfect for understanding how everything connects. 🎥 Watch here: youtube.com/watch?v=Vsq4ey… Tomorrow is the final day of the series.

@syssignals Great bro 😄👍

@Anupam_Devops Recently wrote an article on this topic. Hope this will help readers to understand Git rebase and Merge: x.com/syssignals/sta…

Most people learn Jenkins like this: “Here’s how you write a pipeline” But interviews go like this: 🔥 “Production is down after deployment” 🔥 “CI is failing but local works” 🔥 “Artifacts not downloading” No step-by-step guide. Just chaos. I’ve listed 30 CI/CD scenarios that prepare you for that reality: • Debugging pipelines • Fixing deployments • Handling secrets • Optimizing performance Because DevOps ≠ writing pipelines DevOps = fixing them under pressure.

Most people learn Jenkins like this: “Here’s how you write a pipeline” But interviews go like this: 🔥 “Production is down after deployment” 🔥 “CI is failing but local works” 🔥 “Artifacts not downloading” No step-by-step guide. Just chaos. I’ve listed 30 CI/CD scenarios that prepare you for that reality: • Debugging pipelines • Fixing deployments • Handling secrets • Optimizing performance Because DevOps ≠ writing pipelines DevOps = fixing them under pressure.

WFH to Hybrid to Work from Office 😅