Question 1

What are DORA metrics and why do they matter?

Accepted Answer

DORA (DevOps Research and Assessment) measures four KPIs: deployment frequency (how often you ship), lead time for changes (days from commit to prod), mean time to recovery (MTTR, how fast you fix prod incidents), and change failure rate (% of deploys that break things). Elite teams deploy 100+ times/day with < 1-hour lead time and < 5% failure rate. Measure DORA in your pipelines; it's a morale multiplier and a real proxy for team health.

Question 2

Trunk-based development vs. feature branches, which should I use?

Accepted Answer

Trunk-based (everyone commits to main, behind feature flags) wins. Short-lived feature branches (<1 day) are OK if you squash/rebase. Long branches (> 1 week) = integration hell, slow feedback, merge conflicts. Use feature flags to hide unfinished work, not branches. Reduces CI/CD friction, makes DORA metrics pop.

Question 3

Blue-green vs. canary vs. progressive delivery, when do I use each?

Accepted Answer

Blue-green: instant cutover, full rollback, best for stateless services, instant validation. Canary: 5-10% traffic for 1-2h, catch bugs at scale, preferred for prod. Progressive: gradual ramp (1% → 10% → 50% → 100%) over hours, safest for critical services. Use canary as default; blue-green for low-risk; progressive for high-stakes.

Question 4

How do feature flags fit into CI/CD?

Accepted Answer

Feature flags let you decouple deploy from release: deploy code hidden behind a flag, release it gradually. Enables trunk-based dev, canary testing, instant rollback without re-deploy. Store flags in Unleash, LaunchDarkly, or Harness; evaluate server-side for security. Every advanced CI/CD pipeline uses feature flags now.

Question 5

Monorepo vs. polyrepo, what's the right choice?

Accepted Answer

Monorepo: shared tooling, atomic cross-service deploys, one build pipeline, harder to parallelize. Polyrepo: independent CI/CD per service, easier to scale teams, harder to refactor across repos. Start monorepo for < 3 services; split to polyrepo + monorepo (shared core) as you scale. Google/Meta use monorepo; Netflix/Amazon use polyrepo.

Question 6

How do I speed up build times?

Accepted Answer

Use build caching (Docker layer caching, sccache for Rust, ccache for C++). Run tests in parallel (across N workers). Cache dependencies (pip/npm/cargo). Skip tests on docs-only commits. Use a fast CI platform (Buildkite, CircleCI for parallel, not Jenkins). Target: < 10 minutes for full suite feedback loop.

Question 7

How do I handle secrets in CI/CD pipelines?

Accepted Answer

Never store secrets in code or env vars. Use platform-native secret vaults: GitHub Secrets (encrypted, scoped to repo/env), AWS Secrets Manager, HashiCorp Vault, Doppler. Inject at runtime, never log them, rotate monthly. Scan commits with TruffleHog for accidentally leaked keys.

प्रदेश	ज्युनियर	मध्यम	सीनियर
USA	$110k	$155k	$210k
UK	£70k	£95k	£140k
EU	€75k	€105k	€150k
CANADA	C$125k	C$170k	C$230k

CI/CD Best Practices

CI/CD Best Practices म्हणजे काय

📋 सुरू करण्यापूर्वी

💰 प्रदेशानुसार पगार

🎓 प्रमाणपत्रे

🎯 CI/CD Best Practices वापरणारी करिअर

⚖ यांच्याशी तुलना करा

❓ FAQ

हे कौशल्य तुमच्यासाठी योग्य आहे का, याची खात्री नाही?

तुमचा आदर्श करिअर मार्ग शोधा