---

🚀 Day 2 of My DevSecOps Journey

A Simple & Friendly Breakdown for Everyone

Today, I officially started my journey into DevSecOps — a field that combines Development, Security, and Operations. If that sounds technical, don’t worry! I’ll keep this article simple, visual, and easy to follow.

Let’s jump into what I learned on Day 2👇

🧩 What is DevSecOps?

(Visual Explanation)

Imagine building an app like running a restaurant:

👨‍🍳 Developers — cook the food
🧑‍💼 Operations — serve the food
🛡️ Security — ensure hygiene & safety

Now imagine all three working together from the start.
That’s DevSecOps → fast, safe, reliable software.

🔍 What I Learned Today

---

1️⃣ DevOps vs DevSecOps — Simple View

DevOps        = Dev + Ops  
DevSecOps     = Dev + Sec + Ops (Security added early)

Think of DevSecOps as “DevOps with built-in safety.”

---

2️⃣ How a DevOps Project Works (Visual Flow)

A typical software workflow looks like this:

Code  
   ↓  
Compilation ✔️  
   ↓  
Gitleaks 🔐 (Check secrets)  
   ↓  
SonarQube 📊 (Code quality & bugs)  
   ↓  
Trivy 🛡️ (Dependency scan)  
   ↓  
SBOM 📄 (Ingredients list of the app)  
   ↓  
HashiCorp Vault 🔒 (Store secure info)  
   ↓  
Trivy 🐳 (Container image scan)  
   ↓  
Penetration Testing 🕵️‍♂️

Every arrow is like a quality checkpoint on a production line.

---

3️⃣ Key Features of DevOps (Visual Highlights)

---

4️⃣ Project Environments (Visual Map)

Here’s how software moves before reaching customers:

DEV 🧪 → QA 🔍 → Pre-Prod 🛠️ → PROD 🌍 → DR 🆘

• DEV — developers test

• QA — deeper testing

• Pre-Prod — final rehearsal

• Prod — real users

• DR — backup environment

Not all companies have all of these — some choose based on cost.

---

5️⃣ Deployment Strategies

When new software is released, there are different ways to replace the old version with the new one. Here’s the beginner-friendly breakdown:

---

🔁 Recreate Deployment

How it works:
Old version stops → New version starts

Visual:

[Old ❌] → (Downtime) → [New ✔️]

Downtime: High ❗
Effect on users: Service unavailable for a while
Good for: Simple apps, low traffic systems

---

🔄 Rolling Update

How it works:
New version replaces old version one piece at a time

Visual:

Old ◼️◼️◼️◼️ → New 🟩🟩🟩🟩 (gradual)

Downtime: Very Low
Effect on users: Almost none
Widely used in modern cloud apps

---

🔵🟢 Blue-Green Deployment

How it works:
Two versions run together → Switch traffic instantly

Visual:

Blue (old) ←→ Green (new)
Traffic switches instantly

Downtime: Near Zero
Effect on users: Smoothest experience
Cost: Higher (because two environments run at once)

---

🐤 Canary Deployment

How it works:
Release to a small % of users → then expand if stable

Visual:

5% → 20% → 50% → 100%

Downtime: None
Effect on users: Very safe rollout
Best for: Large apps, customer-facing platforms

---

👥 A/B Testing

How it works:
Different user groups get different versions at the same time

Visual:

Group A → Version A  
Group B → Version B

Purpose: Test what users like
Downtime: None

---

👤➡️👤 Shadow Deployment

How it works:
New version receives copied traffic but isn’t visible to users

Visual:

Real Users → Old Version  
Shadow Copy → New Version (hidden)

Downtime: None
Best for: Safely testing performance at scale

🎯 Day 2 Takeaway

DevSecOps is all about combining:
✅ Speed
✅ Security
✅ Collaboration
✅ Reliability

DevSecOps may sound complex, but the goal is simple:

✨ Build software that is fast, safe, and dependable — from start to finish.

I'm excited for this journey and will share my learning every day!. Today’s learning gave me a strong foundation of how modern teams build, test, and deploy software safely and efficiently.

I’ll be sharing my Day 3 learnings tomorrow — Stay Tuned 🫡