DevOps Model

DevOps is not an SDLC model in the traditional sense — it’s a cultural and technical movement that merges development (Dev) and operations (Ops) into a single, continuous process. The goal: eliminate the wall between “writing code” and “running it in production.”

The DevOps Loop

A continuous cycle of eight stages:

1. Plan — define features and tasks.
2. Code — write the software.
3. Build — compile, package, create artifacts.
4. Test — automated tests (unit, integration, security).
5. Release — prepare for deployment (versioning, approval gates).
6. Deploy — push to production.
7. Operate — run and manage the system.
8. Monitor — track performance, errors, usage. Feedback goes back to Plan.

The infinity symbol (∞) represents the continuous nature — there’s no “end.”

The CAMS Model

Pillar	Meaning	Tools
Culture	Collaboration, shared responsibility, blameless postmortems	—
Automation	Everything that can be automated should be	CI/CD pipelines, IaC
Measurement	Data-driven decisions	Monitoring, observability
Sharing	Share knowledge across Dev and Ops	Documentation, chatops

Key Practices

• CI/CD — every commit is built, tested, and deployed automatically. Jenkins, GitHub Actions, GitLab CI.
• Infrastructure as Code (IaC) — servers configured via code (Terraform, Ansible), not manual SSH.
• Containerization — Docker packages apps with dependencies for consistent behavior across environments.
• Observability — logs, metrics, traces tell you what’s happening in production. Prometheus, Grafana, ELK stack.