INTRODUCTION TO

DEVOP
S DONE BY
ABBAS N
HEMANTH S
 HOW DEVOPS
ARRIVE?
DevOps = Development + Operations
• A culture and set of practices that unifies software
development (Dev) and IT operations (Ops).
• Emphasizes collaboration, automation, and continuous
delivery.
• Focuses on improving communication between teams
and automating processes to enhance software delivery
speed and quality.
• The term 'DevOps' was coined in 2009 by Patrick Debois,
a consultant who saw the gaps between development
and operations teams. The approach grew out of Agile
development principles and Lean practices, which
emphasize flexibility, fast feedback, and continuous
improvement. DevOps is now a movement that focuses
on continuous integration, automated testing, and
deployment. It’s an important part of today’s modern
software development world."
 CHALLENGES BEFORE
DEVOPS

• Development and operations teams working separately led to

inefficiencies.
• Communication delays and misunderstandings slowed down software
deployment.
• Manual processes created bottlenecks and increased the risk of errors.
• Lack of automation affected the overall software quality and reliability.
 DEVOPS
Engineer:
OPERATION
These are the 9 core operations needed to achieve success as a DevOps

1.Application Development – Create a high-quality product that meets

customer needs.
2.Code Coverage – Measure how much of the code runs during automated
testing.
3.Code Developing – Set up the code base required for product development.
4.Configuration – Optimize the product for smooth usability.
5.Deployment – Install the software for end-user access.
6.Orchestration – Arrange multiple automated tasks efficiently.
7.Packaging – Prepare the software for release and deployment.
8.Provisioning – Ensure infrastructure changes align with evolving code
needs.
 DEVOPS
LIFECYCLE
 DEVOPS
LIFECYCLE
Development: Monitoring:
Code is written and version-controlled. Agile Live systems are monitored for performance,
practices are often used to ensure iterative and security, and user behavior. Monitoring helps in
incremental progress. proactive issue detection.

Integration: Feedback:
Code from different developers is integrated Feedback is collected from stakeholders and
regularly using Continuous Integration (CI) tools. users to improve the product continuously.
This helps detect issues early.
Deployment:
Testing: Code is automatically deployed to production
Automated and manual tests are run to ensure using Continuous Deployment (CD) practices for
the code is stable and functions as intended. faster releases.

Operations:
The infrastructure is managed efficiently, ensuring availability, scalability, and
DEVOPS
ARCHITECTURE
 DEVOPS
ARCHITECTURE
 DEVOPS
1. Continuous Integration, Delivery, and
Deployment (CI/CD)
PIPELINE 2) Continuous Delivery (CD)
Continuous Delivery ensures the main branch is always
1) Continuous Integration (CI) in a deployable state.
Continuous Integration is the practice of • Every change passes through automated tests.
frequently committing code changes to a shared • Code is validated in a pre-production environment
source code repository. It ensures that code from that mimics production.
different developers is continuously integrated • Deployment can happen at any time, with the push
and tested to quickly identify and resolve of a button.
conflicts. If management demands a release at 4:30 PM on a
• Key Requirement: Trunk-based development. Friday, the system should be ready and able to deliver
Without frequent commits to a shared branch —confidently and without hesitation.
(like main or trunk), true CI is not achieved—
even if tests and builds are automated.
• Goal: Maintain a consistent, error-free
codebase that integrates everyone's changes.
 DEVOPS
3) Continuous Deployment
PIPELINE 2. Continuous Feedback
Why It Matters
Continuous Deployment goes one step further than Traditional waterfall development suffered from long
delivery—releasing code automatically into delays in feedback, often resulting in products that
production without manual intervention. didn’t meet user needs. Agile shortened that
• Requires robust automated testing and feedback loop—and DevOps accelerates it even
monitoring. further.
• Rarely necessary except for organizations with 1) Continuous Testing
extremely high release frequencies (e.g., Automated testing is essential for early and
hundreds per day). continuous feedback.
Analogy: Think of delivery as FedEx handing you a • Includes unit tests, smoke tests, functional tests,
box. Deployment is you opening and using what’s and end-to-end tests.
inside. If the contents need to be changed after • Tests are integrated at every stage to maintain
delivery, the process has failed. code quality throughout the pipeline.
 DEVOPS
2) Continuous Monitoring
PIPELINE
Monitoring occurs not just in production, but also in
1) Zero Downtime Deployments
Techniques like blue/green deployments ensure no
staging and development environments.
service interruptions:
• Tracks application health, performance, and
• New code is deployed to a non-public environment
infrastructure metrics.
(“green”).
• Helps identify anomalies and issues before they
• Once validated, traffic is switched from the “blue”
impact users.
(active) environment to the green.
Tools monitor everything from cloud and on-prem
resources to application APIs and user-facing
2) Continuous Alerting
performance.
Continuous operations also mean engineers are on-
call and receive real-time alerts.
3. Continuous Operations
• Integrated with monitoring tools to notify staff of
Continuous Operations refers to strategies that
performance or infrastructure anomalies.
ensure maximum uptime and operational continuity.
• Enables rapid response and remediation.
 DEVOPS
TOOLCHAIN
Links in the DevOps Tool Chain
• Build Automation and Source Code
Management
Enables software developers to collaborate and
work in parallel without confusion.
• Continuous Integration
Automatically merges changes from multiple
developers into the baseline source code
repository.
• Application Deployment and
Configuration Management
Manages system installation, activation,
patches, updates, and potential uninstallations.
• Infrastructure Deployment
Enables declarative description and
 KEY DEVOPS
TOOLS
1. Code Repositories
Version-controlled source code repositories (e.g., Git, GitHub) allow multiple developers to work on
code, track changes, and revert to previous versions.
In CI/CD pipelines, code changes trigger automated steps like static analysis or unit tests.
2. Artifact Repositories
Store version-controlled, compiled artifacts (e.g., JFrog Artifactory, Nexus Repository).
3. CI/CD Pipeline Engines
Continuous Integration (CI): Automates code creation, testing, and validation in a shared repository
(e.g., Jenkins, GitLab, CircleCI).
Continuous Delivery (CD): Extends automation to production-level tests and release management.
Continuous Deployment: Adds monitoring and rollback capabilities.
 KEY DEVOPS
TOOLS
4. Containers
• Isolated runtimes (e.g., Docker, Kubernetes) ensure consistency
across environments.
5. Configuration Management
• Tools like Puppet, Chef, and Ansible automate infrastructure
provisioning and enforce policies via code.
6. Cloud Environments
• AWS, Azure, and Google Cloud offer native DevOps tools (e.g.,
AWS CodePipeline, Azure DevOps).
7. Monitoring Tools
• Track performance and security (e.g., New Relic, Dynatrace,
Prometheus, Splunk).
8. As-a-Service Models
• Pre-integrated tool suites for end-to-end DevOps workflows.
 DEVOPS
Tool Description
TOOLS Key Features

- Real-time context-aware reporting- Infrastructure

Widely used DevOps tool for managing infrastructure as modeling and enforcement- Conflict detection &
Puppet
code. remediation- Package inspection across infrastructure-
Speeds up quality software delivery

Open-source IT automation engine for deployment and - Easy to use- Avoids software complexity- Eliminates
Ansible
configuration. repetitive tasks- Manages complex deployments

- Efficient system configuration- Productivity boost- Isolated

Container-based platform for building, shipping, and
Docker containers- Port routing to active containers- Secret
running applications.
management

- Complete OS monitoring- Bottleneck identification-

Monitoring tool for systems, networks, and
Nagios Component monitoring (OS, services, protocols)- Java
infrastructure.
Management Extensions (JMX) support

- High availability- Multi-cloud support- Domain-specific

Chef Cloud-based infrastructure automation using Ruby.
scripting- State-awareness via node inspection
 DEVOPS
Tool Description TOOLS Key Features

CI/CD automation tool for repetitive task - Automation scalability- Web-based configuration- Distributed task
Jenkins
execution and integration. concurrency- 400+ plugin support- Easy maintenance

Distributed version control system for source - Free and open-source- Distributed development- Pull request
Git
code management. support- Fast release cycles- Secure and scalable

Lightweight orchestration tool for managing - Eliminates messy configs- Request tracing- Bug-finding pre-
SaltStack
infrastructure and images. production- Secure access control- Private image registry

Operational intelligence platform for - Next-gen monitoring and analytics- Unified IT view- Extendable
Splunk
machine data analytics. with security modules- Actionable data insights

Web app testing framework for automation - Free and open-source- Android/iOS testing- Keyword-driven
Selenium
across platforms. testing- Regression automation support
 PROS AND CONS OF
Benefits of DevOps DEVOPS Challenges of DevOps

1. Speed – Enables faster innovation and response to market 1. Cultural Shift – Requires major organizational and mindset
changes. change, which may face resistance.

2. Rapid Delivery – Frequent and faster releases improve 2. Tool Complexity – Integration of multiple tools can be
product quality. complex and overwhelming.

3. Reliability – Continuous testing and monitoring ensure stable 3. Skill Gap – Requires skilled personnel in automation, CI/CD,
systems. and cloud infrastructure.

4. Scale – Automation allows scalable and consistent 4. Security Risks – Faster deployments may introduce
infrastructure management. vulnerabilities if not properly managed.

5. Improved Collaboration – Encourages better teamwork and 5. Initial Cost – Setting up DevOps tools and practices can be
shared responsibilities. expensive and time-consuming.

6. Security – Automation and policy as code help maintain

compliance and control.
Cloud as a Platform –
Definition & Key
DEFINITION:

Benefits
• A cloud platform offers a full suite of tools and services available over the
internet, allowing developers to build, test, deploy, and manage applications
without needing to handle the underlying hardware or system-level software.
• This includes everything from virtual machines, databases, and storage, to
development frameworks, APIs, and monitoring tools.

Key Benefits:
1. Faster Development with Reduced Costs:
• Developers can quickly launch and update applications using ready-made tools and automated
workflows, while saving money through a pay-as-you-go model.
2. Scalability and Global Reach:
• Applications can scale easily based on demand and be accessed from anywhere, supporting
remote teams and global user bases efficiently.
Service Models: PAAS (PLATFORM AS
A SERVICE)
IaaS, PaaS, SaaS Offers hardware and software
tools over the internet,
abstracting infrastructure
management. Developers focus
purely on application logic,
accelerating delivery while
reducing operational overhead.
IAAS (INFRASTRUCTURE AS
A SERVICE)
Provides virtualized hardware
resources such as servers,
storage, and networking. Users
retain management of operating
systems, applications, and SAAS (SOFTWARE AS
middleware, giving maximum A SERVICE)
Delivers fully managed software
control and customization
applications accessible via web
browsers. Eliminates local
installation and maintenance,
enhancing user convenience and
ensuring rapid updates.
Cloud Platform Examples & Use
Cases
Amazon Web Services (AWS) Microsoft Azure

Offers extensive cloud services for app hosting, Integrates with enterprise Microsoft products,
serverless computing, and big data analytics. enabling hybrid cloud and AI-driven solutions.

Google Cloud Platform (GCP)

Known for scalable machine learning, data analytics, and container orchestration with Kubernetes.

Use Cases

Application development and hosting, reliable data storage and backup, advanced machine learning
workloads, and scalable Internet of Things (IoT) deployments.
 Advantages & Key Takeaways
Cost-effective
The pay-as-you-go model minimizes upfront capital expenses and optimizes operational budgets.

Scalable
Cloud infrastructure enables rapid resource scaling to meet changing demand without delays.

Reliable
High availability, redundancy, and disaster recovery capabilities ensure business continuity.

Flexible
Users can access services globally from any device, supporting distributed teams and remote workflows.

Cloud platforms are foundational to modern software innovation, enabling organizations to accelerate delivery, optimize
costs, and drive scalable digital transformation.
Get in
touch

Let's
Connect