KEMBAR78
CHP 1 DevOps | PDF | Software Development Process | Agile Software Development
0% found this document useful (0 votes)
18 views9 pages

CHP 1 DevOps

The document provides an overview of DevOps, contrasting it with traditional software development approaches like Waterfall and Agile methodologies. It outlines the objectives, lifecycle, and delivery pipeline of DevOps, emphasizing the importance of collaboration, automation, and continuous improvement. Additionally, it discusses tools, case studies, market trends, and the skills required for a DevOps engineer, highlighting the benefits of implementing DevOps practices in various industries.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
18 views9 pages

CHP 1 DevOps

The document provides an overview of DevOps, contrasting it with traditional software development approaches like Waterfall and Agile methodologies. It outlines the objectives, lifecycle, and delivery pipeline of DevOps, emphasizing the importance of collaboration, automation, and continuous improvement. Additionally, it discusses tools, case studies, market trends, and the skills required for a DevOps engineer, highlighting the benefits of implementing DevOps practices in various industries.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 9

MOD 1 DevOps

Evolution and Introduction to DevOps

1. What is the traditional software development approach?

Answer:
The traditional approach, such as the Waterfall model, involves sequential phases:
requirement analysis, design, implementation, testing, deployment, and maintenance. Each
phase must be completed before moving to the next.

Pros:

• Stable and clear requirements


• Easy to manage

Cons:

• No going back once a phase is complete


• Poor adaptability to change

Example: Government projects often use the Waterfall model due to strict compliance and
documentation needs.

2. What are the limitations of the traditional approach?

Answer:

• Slow adaptation to changing requirements


• Lack of collaboration between teams
• High rework if errors are found late
• Delayed feedback and delivery

3. What is Agile methodology in software development?

Answer:
Agile is an iterative and incremental approach focusing on flexibility, collaboration, customer
feedback, and rapid delivery.

Example:

• Spotify uses Scrum for fast feature delivery.


• Microsoft adopted Agile for Windows 10 with short sprints and regular updates.
MOD 1 DevOps

4. What is DevOps?

Answer:
DevOps is a culture and set of practices that integrates development and operations teams to
collaborate throughout the software lifecycle. It aims for faster delivery, automation, and
continuous improvement.

Definition:
“DevOps is a never-ending process of continual improvement that brings development and
operations teams together.”

Example:
Netflix deploys code changes multiple times a day using DevOps.

5. What is the origin of DevOps?

Answer:

• Early software deployment was manual and slow.


• Conflicts between dev and ops teams led to inefficiency.
• DevOps emerged as a solution around 2009 at the “DevOps Days” conference in
Belgium.

Example:
Flickr deploying 10+ times a day inspired the early DevOps movement.

6. What are the main objectives of DevOps?

Answer:

• Faster Delivery: CI/CD pipelines speed up releases.


• Improved Collaboration: Dev and Ops teams work together.
• Security: Integrated through automation and policies.
• Quality and Reliability: Continuous testing and monitoring improve application
quality.

Example:
Amazon aligns IT with business goals to achieve high system reliability and rapid
innovation.

7. What are the stages in the DevOps Delivery Pipeline?

Answer:
MOD 1 DevOps

1. Plan (Collaborate) – Define goals and sprints.


Example: Jira is used by PMs and devs to plan.
2. Develop (Code) – Developers write code.
Example: Code pushed to Git.
3. Build – Code is compiled and packaged.
Example: Jenkins builds Java into .jar.
4. Test – Automated tests run.
Example: Unit and UI tests for bug detection.
5. Release (Deploy) – Code is deployed.
Example: Docker deploys to staging.
6. Operate – Application runs in production.
Example: Kubernetes handles load balancing.
7. Monitor – Performance is tracked.
Example: Prometheus + Grafana monitor CPU.
8. Feedback – Stakeholders give input.
Example: User reviews added to Jira for future work.

8. What is the DevOps lifecycle?

Answer:

1. Continuous Development – Frequent coding and updates


2. Continuous Integration (CI) – Code merges and builds
3. Continuous Testing – Automated validation
4. Continuous Deployment (CD) – Auto-release to production
5. Continuous Monitoring – Real-time performance checks

Example:
Jenkins (CI), Ansible (Deployment), Prometheus (Monitoring)

9. What challenges does DevOps solve?

Answer:

• Slow deployments
• Missing scripts and dependencies
• Unclear testing strategies
• Slow testing
• Lack of consistent environments
• Reactive firefighting instead of innovation
• Dependence on specific individuals
MOD 1 DevOps

Tools, Case Study & DevOps Ecosystem

10. 🔧 What are the major tools used in DevOps?

Category Tools Purpose

Source Code Management Git, SVN, Jira Version control and issue tracking

Build Tools Maven, Gradle Compiling and packaging code

Testing Tools Selenium, JUnit, TestNG Automated testing

CI Tools Jenkins, Bamboo, Hudson Continuous integration

Deployment Tools Docker, Ansible, Puppet, Chef Automate deployment

Monitoring Tools Nagios, Sensu, New Relic Monitor application health

Example:

• Jenkins pulls code from Git and triggers build/test pipeline.


• Docker + Ansible are used to deploy code automatically.
• Prometheus + Grafana monitor system metrics like CPU, memory.

11. Case Study: eCommerce Platform Failure Without DevOps

Background:

• 4 Developers build an eCommerce application.


• 2 Ops Engineers manage infrastructure.
• Teams work separately in silos.

Problems Faced:

• Code merged only once a week ➝ delays


• Manual testing on local servers ➝ real-world issues missed
• No real-time feedback ➝ bugs found late
• Post-deployment failures ➝ app breaks in production

Failures Identified:

• Client creation fails


MOD 1 DevOps

• Validation issues
• Payment processing errors
• Missing files

Root Cause:

• Lack of Continuous Integration, Automation, and Collaboration

12. Solution with DevOps

DevOps brings:

• Shared responsibility across lifecycle


• Automation using CI/CD and Infrastructure as Code
• Continuous feedback from real-world users
• Agile practices in operations

Benefits Realized:
Benefit Description

Faster Time to Market CI/CD enables faster delivery

High Product Quality Continuous testing identifies bugs early

Better Collaboration Developers and Ops work together

Reduced Downtime Monitoring tools catch issues early

Competitive Edge Faster releases outperform competitors

13. Facebook Case Study: Timeline Feature Rollout

Problem:

• Global rollout of “Timeline” & “Music” features


• Deployment caused high load and instability

DevOps Practices Used:

• Dark Launching: Released to small user group first


• Continuous Monitoring: Tracked errors, usage in real-time
• Rapid Rollback: Problematic features quickly disabled
• Gradual Deployment: Scaled only after stabilization

Outcome:
Facebook scaled successfully to 500M+ users without major downtime.
MOD 1 DevOps

Key Takeaway:
DevOps enables safe innovation, rapid feedback, and fast resolution in production.

14. How DevOps Works in Teams

• Dev and Ops teams are not siloed


• In some models, teams merge into one cross-functional team
• Security is embedded early: called DevSecOps

15. ✅ DevOps Best Practices

Practice Purpose

Continuous Integration (CI) Merge and test code frequently

Continuous Delivery (CD) Deploy code automatically after testing

Microservices Break apps into smaller, manageable services

Infrastructure as Code (IaC) Manage infrastructure using code

Monitoring & Logging Get real-time system health feedback

Collaboration & Communication Break silos between Dev, Ops, QA, Security

16. DevOps Market Trends

📈 Growth:

• 2023 Market Size: ~$10.4 Billion


• Projected by 2028: $25–30 Billion
• CAGR: 20–25%

🏭 Industries Adopting DevOps:

• BFSI: HDFC, JP Morgan (fraud detection)


• eCommerce: Amazon, Flipkart (frequent releases)
• Healthcare: Practo, Mayo Clinic (secure CI/CD)
• Education: Byju’s, Coursera (feature iteration)
• Telecom: Reliance Jio, AT&T (network automation)
MOD 1 DevOps

📌 Trends:

• Rise of DevSecOps: Shift-left security (e.g., Netflix’s Security Monkey)


• AI/ML in DevOps (AIOps): Predict failures, auto-resolve issues (e.g., Facebook)
• Cloud-native DevOps: CI/CD on AWS, GCP, Azure (e.g., Spotify, Adobe)
• Microservices + Containers: Use of Docker, Kubernetes
• Platform Engineering: Internal platforms for self-service deployments

DevOps Ecosystem, Cloud, and Career Skills

17. What is the DevOps Ecosystem?

Definition:
The DevOps Ecosystem includes all tools, practices, teams, and stages that enable
collaboration between development and operations for:

• Faster software delivery


• Automation of repetitive tasks
• Improved software quality
• Continuous monitoring and feedback

18. Real-World DevOps Ecosystem – Example: Netflix

Function Tool/Service Purpose


Source Control Git Code collaboration
CI/CD Jenkins + Spinnaker Fast delivery of microservices
Configuration Mgmt Ansible Automate server setup
Containerization Docker + Titus Scalable, portable deployment
Monitoring Atlas, Prometheus Track system performance
Chaos Testing Chaos Monkey Intentionally break things to test resilience

Key Takeaway:
Netflix deploys hundreds of times per day reliably using its robust DevOps ecosystem.

19. Why is the DevOps Ecosystem Important?

• Promotes cross-team collaboration


• Automates builds, tests, and deployments
• Helps scale systems efficiently
MOD 1 DevOps

• Enables quick feedback and rollbacks


• Moves from weekly → daily → hourly deployments

20. Who is a DevOps Engineer?

A DevOps Engineer bridges the gap between software development and IT operations.
They enable CI/CD, manage infrastructure, write automation scripts, and ensure system
monitoring.

21. Key Skills Required for a DevOps Engineer

Skill Area Examples


Linux & Scripting Bash, Python
Version Control Git, SVN
CI/CD Tools Jenkins, CircleCI
Configuration Mgmt Puppet, Ansible
Containers & Orchestration Docker, Kubernetes
Cloud Platforms AWS, Azure, GCP
IaC Terraform, CloudFormation
Monitoring & Logging Prometheus, Grafana
DevSecOps Knowledge Security tools & automation
Soft Skills Communication, collaboration, problem-solving

22. Example Job Description (Infosys)

Role: DevOps Engineer


Skills Required:

• Git, Jenkins, Ansible


• Docker, Kubernetes
• AWS or Azure experience
• CI/CD pipeline setup
• Monitoring with Prometheus, Grafana
• Scripting in Python or Bash

23. What is DevOps on the Cloud?


MOD 1 DevOps

Definition:
DevOps on the cloud means applying DevOps practices like automation, CI/CD, monitoring,
and IaC using platforms like AWS, Azure, GCP.

24. Benefits of DevOps on the Cloud

Benefit Explanation
Speed Automate builds & deploy faster
Scalability Adjust to growing traffic
Reliability Auto-recovery & monitoring
Cost-Efficiency Pay-as-you-go model
Global Reach Deploy apps worldwide in minutes

25. Netflix on AWS Cloud – DevOps in Action

Function Tool/Service Purpose


Infrastructure AWS EC2, S3, Lambda Scalable servers
CI/CD Jenkins + Spinnaker Auto build/deploy
Containerization Titus + Docker Container orchestration
Monitoring Atlas + CloudWatch Real-time metrics
Chaos Testing Chaos Monkey Break systems for resilience
IaC AWS SDK Scripts Automate infrastructure

Result:
Netflix achieves high availability and deploys hundreds of times per day globally with
minimal downtime.

26. More Real-World DevOps Examples

• Spotify (Google Cloud):


Jenkins, Kubernetes, Cloud Build, Stackdriver
• Etsy (AWS):
Terraform, Kubernetes, Jenkins
• Adobe (Azure):
Azure DevOps tools for CI/CD and collaboration

You might also like