DevOps
Dr. N. Sivaranjani
Module 1: Introduction
1 DevOps Overview 2 Business Needs
Introduction to DevOps concepts Why organizations adopt DevOps
and principles. for success.
3 DevOps Origins 4 Core Practices
Evolution from Agile and early Key practices like CI/CD and
influencers. Infrastructure as Code.
5 DevOps Practices 6 DevOps Culture
How people unite to provide value Companies align their people,
to customers. processes, and tools
7 Process and Technology 8 DevOps Myths
in DevOps
DevOps: Definition
DevOps is a transformative culture and practice that unites software development (Dev) and IT
operations (Ops) teams.
Software Development Lifecycle
Water Fall Model
Its lifecycle holds different phases
and this phase happens one after the another in a
sequential manner
Pros & Cons
PROS CONS
Simple and easy method to understand and End products are tagged with high risk and
use. uncertainty.
Review happens in each phase making it less Working models are not produced until we reach the
prone to errors. end phase.
Most reliable model for small projects. It is not suitable for complex and long-term projects.
Every phase happens one at a time, so Difficult to accommodate frequent requirement
overlapping issues are avoided. changes.
Difficult to measure the progress of the project at mid
phases.
Since testing and integration are done at the end, early
detection of challenges or bottlenecks is difficult.
Software Development Lifecycle
Agile Methodology
It includes an incremental approach like the
waterfall model along with an additional focus
on an iterative process.
Incorporating frequent business needs or
changes and speeding the release process.
Pros & Cons
PROS CONS
It accommodates change at any time In case of a small-scale project, Agile can’t be
Gives importance to customer feedback implemented.
throughout the entire lifecycle. Less Documentation leads to costly
It provides the ability to scale up and maintenance, face a challenge to rectify errors
down easily. and the entire process to look back is time-
consuming
Provides a continuous delivery
Continuous monitoring and attention are There is a gap between the development and
provided which improves the product operations teams.
quality. The final product might look different than the
It reduces the overall time needed for actual planned one
development. Frequent meetings
Stakeholders like customers, developers,
and product owners focus more on
customer needs rather than processes and
tools.
DevOps: An Overview
DevOps is a set of practices that combines
software development and IT operations.
It emphasizes collaboration, communication,
and automation to deliver software faster and
more reliably.
The goal is to improve the efficiency and
effectiveness of software delivery by breaking
down silos between development and operations
teams.
DevOps: An Overview
DevOps is a set of practices that combines
software development and IT operations.
It emphasizes collaboration, communication,
and automation to deliver software faster and
more reliably.
The goal is to improve the efficiency and
effectiveness of software delivery by breaking
down silos between development and operations
teams.
DevOps: An Overview
DevOps is a set of practices that combines
software development and IT operations.
It emphasizes collaboration, communication,
and automation to deliver software faster and
more reliably.
The goal is to improve the efficiency and
effectiveness of software delivery by breaking
down silos between development and operations
teams.
What is DevOps?
1 Definition
Combines development and operations for better
software delivery.
2 Goals
Speed, quality, collaboration, and reliability in
software delivery.
3 Core Pillars
Automation, CI/CD, collaboration, and monitoring.
Challenges Before DevOps
Siloed Teams
Lengthy Development Cycles
Inefficient Communication
Inconsistent Deployments
Slow Response to Market Needs
Why Businesses Need DevOps
1. Faster Time-to-Market
Automates testing and deployment for frequent, reliable releases.
Example: Amazon deploys every 11.7 seconds.
2. Improved Product Quality
Automated testing and monitoring catch bugs early.
3. Enhanced Collaboration
Breaks silos, fosters shared ownership, and uses collaboration tools (e.g., Slack, Jira).
4. Cost Efficiency
Reduces manual effort, downtime, and defects through automation.
5. Increased Customer Satisfaction
Faster, reliable feature releases improve user trust and retention.
Real-World Examples
Netflix
• Problem: Needed constant innovation while maintaining reliability.
• Solution: Automated CI/CD pipelines and Chaos Engineering.
Etsy
• Problem: Deployment issues caused outages.
• Solution: Reduced deployment times and improved reliability
DevOps Origins
Agile Development Continuous Integration and Delivery (CI/CD)
Agile methodologies, emphasizing iterative development and CI/CD practices facilitated automated builds, testing, and
customer feedback, laid the foundation for DevOps. deployment, leading to a more streamlined and efficient
software delivery process.
1 2 3
Infrastructure as Code
Treating infrastructure as code enabled automation and
consistency, paving the way for faster and more reliable
deployments.
DevOps Practices
1 Continuous 2 Continuous Delivery
Integration
Automating the deployment
Regularly merging code process, ensuring fast and
changes into a shared reliable delivery of software
repository, enabling early updates to production
detection and resolution of environments.
integration issues.
3 Infrastructure as Code 4 Monitoring and
Logging
Defining infrastructure
using code, allowing for Monitoring system
consistent and repeatable performance and collecting
deployments, reducing logs to identify and address
manual errors and issues proactively, ensuring
improving efficiency. system stability and
reliability.
DevOps Culture
Collaboration Communication Automation
Encourages cross-functional teams Promotes open communication Emphasizes automating repetitive
to work together seamlessly, channels, facilitating transparent tasks, freeing up teams to focus on
breaking down silos and fostering information flow and fostering a innovation and problem-solving,
knowledge sharing. culture of shared responsibility. leading to increased efficiency and
productivity.
Process and Technology in DevOps
Planning Development Deployment Monitoring and Feedback
Defining project goals, Building and testing software Automating the process of Continuously monitoring
requirements, and timelines, code, using agile deploying software updates to system performance, collecting
ensuring a clear understanding methodologies and production environments, logs, and analyzing data to
of the scope and objectives. collaborating with operations ensuring consistent and identify and address issues,
teams to ensure code quality reliable deployments, reducing improving software stability
and alignment with manual errors and downtime. and reliability, providing
infrastructure requirements. valuable feedback for
continuous improvement.
DevOps Myths
Myth Reality
DevOps is just about DevOps emphasizes
automation. collaboration,
communication, and cultural
change, not just automation.
DevOps is only for large Organizations of all sizes can
organizations. benefit from DevOps
practices, adopting them
incrementally to fit their
needs.
DevOps is a silver bullet. DevOps requires a holistic
approach, involving cultural
changes, process
improvements, and
technology adoption.
Benefits of Adopting DevOps
Faster Time to Market Improved Quality
Reduced delivery times allow for Continuous integration and
faster responses to market changes automated testing ensure high-
and faster iterations of products. quality software releases, reducing
bugs and improving customer
satisfaction.
Increased Productivity Enhanced Employee Morale
Streamlined processes and Collaboration and shared
automation free up teams to focus on responsibility lead to a more
innovation and problem-solving, engaging work environment,
leading to higher productivity. boosting employee morale and job
satisfaction.
Key Metrics for Success
Deployment Frequency: How often features are released.
Lead Time for Changes: Time from idea to deployment.
Mean Time to Recovery (MTTR): Speed of issue resolution.
Change Failure Rate: Percentage of failed deployments.
Challenges and Obstacles in
DevOps Adoption
1 Cultural Resistance 2 Lack of Skills
Changing established Implementing DevOps
workflows and breaking down requires specialized skills in
silos can face resistance from automation, cloud computing,
employees accustomed to and continuous delivery, which
traditional ways of working. may require training and
development programs.
3 Tool Integration 4 Security Concerns
Complexity
Automating deployments and
Integrating various tools and integrating with cloud
technologies across the platforms can raise security
software development lifecycle concerns, requiring careful
can be complex and time- planning and implementation
consuming. of security measures.
The Future of DevOps
Cloud-Native Technologies Artificial Intelligence (AI) Data-Driven Decision-Making
DevOps will continue to embrace AI and machine learning will play
cloud-native technologies, an increasingly important role in DevOps will increasingly rely on
leveraging serverless computing, DevOps, automating tasks, data analytics to gain insights,
microservices, and containerization optimizing processes, and identify patterns, and optimize
for greater scalability and flexibility. improving decision-making. performance, enhancing efficiency
and effectiveness.
