0% found this document useful (0 votes)
33 views10 pages

R21 DevOps Unit - 2

Uploaded by

vignesh varma
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
33 views10 pages

R21 DevOps Unit - 2

Uploaded by

vignesh varma
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 10

R21 DevOps

Unit II
Fundamentals of DevOps
Yerram Sneha
Agenda

3. DevOps 4. DevOps
1. Need for 2. DevOps
Architectur Delivery
DevOps Ecosystem
e Pipeline

7.
5. 6. Instances
Deploymen Orchestrat of
ts ion Applicatio
ns
Need for DevOps
Challenges in Traditional Software
Development:
 Long release cycles
 Lack of collaboration between development
and operations teams
 Inability to adapt to rapid changes
Why DevOps?:
 Faster delivery,
 improved collaboration,
 continuous feedback
Benefits of DevOps:
 Shorter time-to-market
 Continuous delivery of quality software
 Reduced errors through automation
DevOps Ecosystem
Cultural Shift:
 Breakdown of silos between Dev, Ops,
and QA
 Collaboration and shared responsibilities

Tools in the DevOps Ecosystem:


 Git for version control
 Jenkins for Continuous Integration (CI)
 Docker for containerization
 Kubernetes for orchestration

The Importance of Automation:


 Automated testing, deployment, and
monitoring
DevOps Delivery
Pipeline
Stages of the Pipeline:
 Continuous Integration (CI): Code is integrated frequently and automatically tested.
 Continuous Delivery (CD): Every change is tested and prepared for release to production.
 Continuous Deployment: Automates the release to production for every change that passes testing.

Benefits of Automation:
Reduced human errors Tools:
Faster feedback loops for quicker iterations Jenkins, GitLab CI/CD, TravisCI for automating CI/CD
Deployments
Deployment Strategies:
 Blue-Green Deployment: Two identical
environments—switch traffic when the new
version is ready.
 Canary Releases: Deploy new versions to a
small subset of users before wider rollout.
 Rolling Deployments: Incrementally deploy
new updates across servers.
Automated Deployment Tools:
 Ansible, Kubernetes, Chef for seamless
deployments
Rollback Mechanisms:
 Automated rollbacks in case of failures to
ensure system stability
Orchestration
Introduction to Orchestration:
 Orchestration of containers (e.g., Docker) across multiple hosts
 Managing the lifecycle of containers (start, stop, scale)
Tools for Orchestration:
 Kubernetes: Automates deployment, scaling, and management of containerized
applications
Scaling Applications Automatically:
 Ensures applications handle increased loads dynamically
Automating Workflows:
 Orchestrates the execution of complex workflows with dependencies
Instances of
Case Studies of DevOps
Implementation: Applications
 Netflix: Continuous delivery pipeline for
rapid software updates
 Amazon: Microservices architecture and
automated deployments
 Etsy: Success with Continuous
Deployment and automated rollback
strategies
Industry Applications:
 DevOps in e-commerce, banking, social
media for reliable, scalable software
development
Success Stories and Lessons Learned:
 Reduced deployment time, faster
feedback, and improved system
reliability

You might also like