UNIT-1

What is Agile Model

The Agile Model was primarily designed to help a project adapt quickly to change requests.
So, the main aim of the Agile model is to facilitate quick project completion. To accomplish
this task, agility is required. Agility is achieved by fitting the process to the project and
removing activities that may not be essential for a specific project. Also, anything that is a
waste of time and effort is avoided. The Agile Model refers to a group of development
processes. These processes share some basic characteristics but do have certain subtle
differences among themselves.

Definition:2

Agile development is a term that's used to describe iterative software development. Iterative
software development shortens the DevOps life cycle by completing work in short
increments, usually called sprints. Sprints are typically one to four weeks long. Agile
development is often contrasted with traditional or waterfall development, which plans larger
projects up front and completes them according to the plan.

Delivering production quality code every sprint requires the Agile development team to
account for an accelerated pace. All coding, testing, and quality verification must be done
each and every sprint. Unless a team is properly set up, the results can fall short of
expectations. While these disappointments offer great learning opportunities, it's helpful to
learn some key lessons before getting started.

DevOps
DevOps is a software development practice that combines software development and IT
operations. It uses a combination of tools, practices, and a cultural philosophy to improve the
software development lifecycle.

 Focus: Speed and agility

 Practices: Streamlining and automating software development and deployment
processes
 Tools: Automation tools, CI/CD pipelines, containerization, and cloud technologies
 Benefits: Expedites new release cycles, reduces deployment risk, and increases user
feedback loops

Benefits of DevOps

 Faster delivery: DevOps can reduce the time it takes to develop and deploy
software.

  Better quality: DevOps can improve the quality and security of software.
  Faster response to customers: DevOps can help organizations respond to customer
needs more quickly.
  Better collaboration: DevOps can improve communication and collaboration between
development and operations teams.

How DevOps works

 DevOps teams use automation to reduce manual tasks and errors.

  DevOps teams use tools like continuous integration and delivery (CI/CD) to improve
software quality and security.
  DevOps teams use monitoring and analytics tools to analyze how code changes affect
the overall environment.

 DevOps history


The DevOps movement started around 2007 when software development and IT operations
teams became concerned with the traditional software development model.
DevOps tools
Some examples of DevOps tools include AWS CodePipeline, Azure DevOps, and Google
Cloud Deployment Manager.

Agile development in DevOps

It refers to the practice of integrating Agile methodologies, which focus on iterative
development with short feedback loops, into a DevOps pipeline, enabling rapid software
delivery through continuous integration, testing, and deployment, ultimately allowing for
faster releases and greater flexibility to adapt to changing requirements.

Key points about Agile development in DevOps:

Iterative approach:

Agile development breaks down projects into small, manageable "sprints" where teams
deliver working software increments regularly, aligning with the DevOps philosophy of
continuous delivery.

  Collaboration and communication:

Both Agile and DevOps emphasize strong cross-functional team collaboration, allowing
developers, testers, and operations teams to work closely together throughout the
development cycle.
  Automated testing:
Agile development within DevOps heavily relies on automated testing to ensure quality and
provide rapid feedback on code changes, which is crucial for frequent deployments.
  Continuous integration (CI):
A core practice in both Agile and DevOps, where code changes are frequently integrated into
the main codebase, triggering automated builds and tests.
  Continuous delivery (CD):
This practice ensures that software is always ready for production deployment, allowing
teams to release new features quickly and reliably.

Benefits of integrating Agile and DevOps

Faster time to market:

By streamlining the development process with automation and frequent releases, teams can
deliver new features to customers more quickly.

  Improved quality:
Continuous testing and feedback loops throughout the development process help identify and
resolve issues early on, resulting in higher quality software.
  Increased adaptability:
Agile practices allow teams to respond to changing requirements and market conditions more
effectively.
  Enhanced collaboration:
Breaking down silos between development and operations teams fosters better
communication and collaboration.

What is ITIL
ITIL stands for Information Technology Infrastructure Library. It’s actually used to guide it
team to improve the value of service by focusing on solving the business issues and creating
business value. One of the important parts of ITIL is the configuration management database
which provides services, users, software, hardware, documents, and IT components to the
central authority. ITIL has been adopted by thousands of organizations worldwide like
Microsoft, NASA, and HSBC. ITIL’s current version which is use in the market is ITIL4, it
provides a practical and flexible basis to support organizations for a digital transformation.

ITIL

 Focus: Stability and reliability

 Practices: Service strategy, design, transition, operation, and continual improvement
 Tools: Incident management systems, service desks, and configuration management
databases (CMDBs)
 Best practices: Service Level Agreements (SLAs) to reduce customer confusion and
complaints

ITIL and DevOps Together

ITIL and DevOps are frameworks that can be used together to improve IT service
management (ITSM). ITIL provides a structured approach to ITSM, while DevOps focuses
on streamlining and automating software development and deployment.

Benefits of using ITIL and DevOps together

  Reduce customer confusion

ITIL's SLAs can reduce confusion and complaints by outlining what has been promised to a
customer

  Reduce incidents
Combine ITIL's incident management processes with DevOps' automation to reduce
incidents
  Improve collaboration
Automation can improve collaboration between stakeholders
  Increase release success
DevOps' automated deployment pipeline can increase the success rate of releases.

Misconceptions about DevOps vs. ITIL :

1. DevOps can replace ITIL: There are essential business functions like service
Management, support, operation, governance, and costing these processes are
important and they both given by DevOps and ITIL, only DevOps or ITIL can’t
provide them.
2. ITIL is always documentation: It’s actually not true information ITIL is what the
team makes the choice the rules are made by team, ITIL has Its own guidelines but
the decision is always made by the IT team.
3. ITIL is only for large companies: It’s true that ITIL is used by large enterprises but
Its guidelines can also benefit small businesses, small business only needs to know
how to handle change management, major incident, and knowledge management.

Use cases for DevOps and ITIL :

IT needs both ITIL and DevOps elements.

DevOps is an automated development, collaboration, and blame-free culture.

It’s better collaboration between IT and business when we use ITIL and DevOps together and
it also helps in customer satisfaction due to the improved delivery of services and better
management of issues. ITIL provides a tried-and-true starting point, where DevOps can add
improvement with the blameless examination, automation, and other collaborative
approaches which makes every IT process easier.

Difference between DevOps and ITIL :

S.NO. DevOps ITIL

DevOps refers to effective
ITIL refers to a set of detailed guidelines for
collaboration between the
01. effective and efficient management of an
development team and operations
organization’s IT services.
team.
Use a methodical approach to
It uses a systematic approach to manage the IT
02. minimize the friction between two
service to ensure growth.
teams.
 CI and CD are the backbone of
03. ITIL aims to increase the delivery process.
modern DevOps philosophy.
Continuous integration and
Services are built, discuss, tested, and
04. continuous delivery are critical to
implemented.
increasing.
DevOps focus on the concept. It has a dynamic
DevOps focus on the concept. It has
05. body of knowledge. ITIL focus on development.
a dynamic body of knowledge.
It has a static body of knowledge.

DevOps processes

The meaning of DevOps processes is pretty much connected to the DevOps description
itself. When we talk about the DevOps process we refer to the cycle of established DevOps
phases that enables efficient software development. The combination of DevOps
methodologies, practices, and tools organized in the DevOps loop is what creates the agile
intake process

The DevOps process involves several steps, including planning, building, testing, and
releasing code. The goal of DevOps is to streamline the flow of information between
development and operations teams to improve efficiency and collaboration.
Steps in the DevOps process

 Planning: Define objectives and goals, and create a design based on requirements

  Building: Introduce code to the project, and rebuild if necessary

  Testing: Ensure the project performs as planned, and test for edge and corner cases
 Releasing: Verify the code is ready for deployment, and perform a final check for
production readiness
  Deploying: Deploy the project if it meets all requirements and has passed all tests
  Monitoring: Identify and measure metrics like deployment frequency, lead time, and
mean time to recovery

Other considerations

 Use an agile methodology like scrum

 Use Git-based source control
 Integrate source control with work tracking
 Automate software deployment and testing
 Adopt cloud computing
 Use build tools and containerization
 Use configuration management
 Streamline the flow of information between teams

What is Continuous Delivery in Devops?

Continuous Delivery (CD) is an important part of DevOps that helps teams deliver software
updates quickly and safely.
Continuous Delivery (CD)

Continuous Delivery (CD) automates the steps of building, testing, and deploying software. It
ensures that code changes are always ready for deployment with minimal manual
intervention.

 Aims to reduce costs, accelerate development, and lower risks while maintaining code
quality
 Involves creating a release pipeline that automates infrastructure creation and
deployment of new builds.
 Continuous integration ensures code worked by several developers across multiple
locations is always integrated into a common repository.
 Configuration management makes it possible to abstract away the complexities of a
product into simple configurations.
 Test-driven development ensures that the code can be tested and deployed, all in a
matter of a few minutes.

Continuous Integration(CI)

There could be scenarios when developers in a team, work in isolation for an extended period
and only merge their changes to the master branch once their work is completed. This not
only makes the merging of code very difficult, prone to conflicts, and time-consuming but
also results in bugs accumulating for a long time which are only identified in later stages of
development. These factors make it harder to deliver updates to customers quickly.

With Continuous Integration, developers frequently commit to a shared common repository

using a version control system such as Git. A continuous integration pipeline can
automatically run builds, store the artifacts, run unit tests, and even conduct code reviews
using tools like Sonar. We can configure the CI pipeline to be triggered every time there is a
commit/merge in the codebase.

Role of CD in the CI Pipeline

CD builds on continuous integration (CI) by automating the deployment of code changes to

testing or production environments after the build and testing stages.

At its core, continuous delivery follows a streamlined process known as the continuous
delivery pipeline for cloud computing environments. The pipeline begins with the developer
or development team committing their code to the source repository. Automated tests (unit,
regression, performance, etc.) are run for every check-in to ensure high-quality code. Once
the code is verified, the executables are deployed automatically to an intermediate
environment such as staging, integration, or UAT. At this point, the code is ready to go into
production and can be pushed live on demand.

For continuous delivery to work effectively, fundamental principles should be in place. Of

the many aspects of continuous delivery, the three significant pillars are continuous
integration, configuration management, and test-driven development.

 Continuous integration ensures code worked by a developer across multiple locations

is always integrated into a shared repository. This avoids the chaos that results from
bulky and conflicting code commits.
 Configuration management makes it possible to abstract away the complexities of a
product into simple configurations. It makes the software flexible, scalable, and
lightweight.
 Test-driven development is what makes continuous delivery what it is. It ensures that
the code can be tested and deployed, all in a matter of a few minutes. It has shifted the
software delivery model from deployments scheduled across weeks or months to
multiple releases in a single day.

Some Benefits of Continuous Delivery:

 Faster Releases: Helps teams get features and updates to customers more quickly.
 Lower Risk: Reduces the chances of problems during releases by making smaller
changes more often.
 Better Teamwork: Improves communication and collaboration between developers
and operations teams.
 Higher Quality: Leads to better software by catching bugs early through regular
testing.
 More Flexibility: Allows teams to quickly respond to customer feedback and changes
in the market.

Popular CD Tools:

 Jenkins: Open-source automation server for CI/CD.

 GitLab CI/CD: Integrated CI/CD solution within GitLab.
 CircleCI: Cloud-based platform for robust CI/CD pipelines.
 Azure DevOps: Comprehensive CI/CD and DevOps tool by Microsoft.

To make CD effective, implement strong automated testing and maintain streamlined

deployment pipelines to minimize manual work and reduce risks.
What is Release Management?

In the world of software development, release management plays a pivotal role in ensuring
the smooth and efficient delivery of software products. It serves as a bridge between the
development and operations teams, allowing for effective collaboration and coordination
throughout the software development lifecycle.

Release management in DevOps refers to the comprehensive set of practices and processes
involved in planning, scheduling, coordinating, and controlling the release of software
applications or updates. It aims to minimize risk, ensure quality, and maximize the value of
software releases to end-users or customers.

Key Components of Release Management

1. Planning and Coordination

Release planning involves identifying the scope of a release, defining its objectives, and
establishing a timeline for its delivery. It also includes coordinating with various
stakeholders, such as developers, testers, operations teams, and business units, to align their
efforts and ensure a successful release.

2. Environment Management

Effective release management requires the establishment and maintenance of consistent and
reliable environments for development, testing, and production. This involves managing the
configuration of infrastructure, software dependencies, and data to ensure compatibility and
minimize potential issues during deployment.

3. Release Deployment

The deployment phase of release management involves the actual installation, configuration,
and activation of the software release on target environments. It relies on automation and
deployment tools to streamline the process and reduce the risk of errors or downtime.

4. Testing and Quality Assurance

Thorough testing is a critical aspect of release management. It involves conducting various

types of testing, including unit testing, integration testing, regression testing, and user
acceptance testing, to validate the functionality, performance, and security of the software
release.

5. Change Management

Change management is an integral part of release management, as it involves assessing and

managing the impact of changes introduced in a release. This includes evaluating potential
risks, communicating with stakeholders, and implementing strategies to minimize disruption
and ensure a smooth transition.
6. Release Monitoring and Feedback

Monitoring the performance and stability of a released software application is crucial for
identifying and addressing any issues or bugs. Gathering feedback from end-users and
stakeholders helps to continuously improve the software and enhance future releases.

Benefits of Effective Release Management

Implementing a robust release management process in DevOps offers several benefits,
including:

1. Reduced Risk

By following standardized release processes and conducting thorough testing, release

management minimizes the risk of introducing bugs, vulnerabilities, or compatibility issues
into production environments.

2. Faster Time to Market

Efficient release management allows for shorter deployment cycles, enabling organizations to
deliver new features, enhancements, or bug fixes to end-users more frequently. This agility
enhances customer satisfaction and keeps businesses competitive.

3. Improved Collaboration

Release management promotes collaboration and communication between development,

operations, and other teams involved in the software delivery process. This alignment ensures
that everyone is working towards a common goal, resulting in a smoother and more efficient
release.

4. Increased Stability and Reliability

By implementing controlled and standardized release processes, organizations can maintain

the stability and reliability of their software applications. This reduces system failures,
downtime, and the negative impact on end-users.

In the realm of DevOps, release management serves as a critical function to ensure the
successful delivery of software applications. By planning, coordinating, and controlling the
release process, organizations can minimize risks, enhance collaboration, and deliver high-
quality software products to their customers.

Scrum
Scrum is a framework of roles, rules, artifacts, and events used for implementing Agile
projects. This iterative approach to software development consists of ‘sprints’ that generally
last for one to four weeks, ensuring regular delivery of new product versions.
Scrum is just a simple framework for complex product development that is based on values
and principles. Scrum is not a prescriptive methodology that tells you how your process
should look like. Scrum is highly focused on what is happening during the Sprint. Scrum will
not tell you how your process within the Sprint should look like. Scrum is an additive
framework, what that means is Scrum will only tell you the minimum sets of what you need
to have so that you can claim you are using Scrum. The same as when you need to install a
software on your computer, there is a minimum requirement for the computer
specification. But it is not illegal to install the software on a computer that is above the
minimum specification. So with this premise, it is not illegal to add practices that will
enhance the flow of your value delivery within the Scrum Framework.
 A framework that helps teams work in short cycles
 Emphasizes collaboration, flexibility, and responsiveness to change
 Uses a semi-prescriptive approach to minimize ambiguities
 Helps organize complicated tasks into user stories
 Clear differentiation of roles and ceremonies
 Quick release cycles

Benefits of using Scrum and DevOps together

 Improved software quality, speed, and reliability

 Reduced risk
 Decreased time to market
 Higher return on investment (ROI)
kanban
The Kanban method is an approach to evolutionary and incremental systems and process
change for organizations. A work-in-progress limited pull system is the central mechanism to
uncover system operation (or process) complications and encourage collaboration to
continuously improve the system.

Electronic Kanban boards are also available in ALM tools like Rally (CA Agile), Jira, Swift,
Kanban, LeanKit, Kanban, etc. Stages could be configured in these tools, and the movement
of tickets between stages could be viewed in these tools.

Kanban in DevOps is a visual tool that helps teams manage work items and track progress in
a project. It's a common framework for agile and DevOps software development.
How it works

 Kanban boards are split into columns that track each stage of a project.

  Work items are placed as "cards" in the columns.

  Work moves from left to right on the board.
  Teams pick work from the column to the left when they're done with their current work
items.

Benefits

 Kanban boards help teams visualize their workflow.

 They help teams limit work in progress.
 They help teams optimize their workflow.
 They provide transparency of work and team capacity.

Kanban principles start with what you know, pursue incremental change, respect the current
process, and encourage leadership at all levels.

A delivery pipeline in DevOps is a series of automated steps that code changes go through
from development to production. It's made up of interconnected stages, each with a specific
task.

DevOps pipeline
Stages of a DevOps pipeline

 Continuous integration (CI)

Frequent commits to a source code repository, so that conflicts between developers'

code changes are quickly identified

  Continuous testing
Automated tests are run on the code to ensure its usability and suitability
  Continuous delivery (CD)
Validated code changes are put into select environments or code repositories
  Continuous deployment
The release and deployment of software into production environments is automated
  Continuous operations
The efficient management of hardware and software upgrades to reduce the need for planned
downtime
  Continuous monitoring
The validation of the environment's stability and verification that the applications are doing
what they're designed to do

Benefits of a DevOps pipeline

 Faster delivery of new features and bug fixes to end-users

 Immediate feedback on the impact of code changes in the production environment
 Greater agility and responsiveness to market demands

Tools for DevOps pipelines

Jenkins, Bamboo, and GitLab are some tools that can be used to create a
DevOps pipeline.

Bottlenecks
Bottlenecks in DevOps are obstacles that slow down the software development life cycle
(SDLC). They can be caused by a number of factors, including a lack of resources, poor
planning, or competing incentives.
Causes of bottlenecks

 Misaligned incentives: Developers may be incentivized to deliver quickly, while

operations may be incentivized to prioritize security and reliability

  Legacy processes: Outdated change management processes can slow down the
development cycle
  Lack of resources: A shortage of testing or QA personnel or facilities can cause
bottlenecks
  Manual processes: Manual tasks can slow down the development cycle

How to identify bottlenecks

 Use monitoring tools to track resource utilization, build and deployment times, and
performance metrics

  Run automated and load tests to simulate peak usage scenarios

  Perform stress tests to determine how well a system can handle extreme increases in
load
  Analyze log files to identify issues
How to resolve bottlenecks

 Optimize code quality

 Streamline CI/CD workflows
 Parallelize tasks
 Scale infrastructure
 Use efficient deployment strategies
 Optimize database performance
 Leverage CDNs for content delivery

UNIT-2

Software development models and DevOps

Software modeling is the process of designing software applications before coding, while
DevOps is a software development methodology that emphasizes collaboration and
automation.

Software modeling

 Involves designing software applications before coding

 An essential part of the software development process

DevOps

 Combines development (Dev) and operations (Ops)

  Emphasizes collaboration and communication between development and operations

teams
  Uses automation to improve software quality and reliability
  Uses continuous integration to merge code changes into a central repository
  Uses continuous delivery to automate the delivery of applications to cloud
infrastructure environments
  Uses automation to reduce the risk of human error and make products easier to scale

DevOps aims to shorten the software development lifecycle and improve the quality and
reliability of software releases. It can result in a competitive advantage for businesses and
their customers.
DevOps Lifecycle

DevOps defines an agile relationship between operations and Development. It is a process that is
practiced by the development team and operational engineers together from beginning to the final
stage of the product.

Learning DevOps is not complete without understanding the DevOps lifecycle phases. The DevOps
lifecycle includes seven phases as given below:

7 Cs of DevOps:
1. Continuous Development

2. Continuous Integration

3. Continuous Testing
 4. Continuous Deployment/Continuous Delivery

5. Continuous Monitoring

6. Continuous Feedback

7. Continuous Operations

1. Continuous Development

In Continuous Development code is written in small, continuous bits rather than all at once,
Continuous Development is important in DevOps because this improves efficiency every
time a piece of code is created, it is tested, built, and deployed into production. Continuous
Development raises the standard of the code and streamlines the process of repairing flaws,
vulnerabilities, and defects. It facilitates developers’ ability to concentrate on creating high-
quality code.

2. Continuous Integration

Continuous Integration can be explained mainly in 4 stages in DevOps. They are as follows:

1. Getting the SourceCode from SCM

2. Building the code

3. Code quality review

4. Storing the build artifacts

The stages mentioned above are the flow of Continuous Integration and we can use any of the
tools that suit our requirement in each stage and of the most popular tools are GitHub for
source code management(SCM) when the developer develops the code on his local machine
he pushes it to the remote repository which is GitHub from here who is having the access can
Pull, clone and can make required changes to the code. From there by using Maven we can
build them into the required package (war, jar, ear) and can test the Junit cases.SonarQube
performs code quality reviews where it will measure the quality of source code and
generates a report in the form of HTML or PDF format. Nexus for storing the build
artifacts will help us to store the artifacts that are build by using Maven and this whole
process is achieved by using a Continuous Integration tool Jenkins.

3. Continuous Testing

Any firm can deploy continuous testing with the use of the agile and DevOps methodologies.
Depending on our needs, we can perform continuous testing using automation testing tools
such as Testsigma, Selenium, LambdaTest, etc. With these tools, we can test our code and
prevent problems and code smells, as well as test more quickly and intelligently. With the aid
of a continuous integration platform like Jenkins, the entire process can be automated, which
is another added benefit.
4. Continuous Deployment/ Continuous Delivery

Continuous Deployment: Continuous Deployment is the process of automatically deploying

an application into the production environment when it has completed testing and the build
stages. Here, we’ll automate everything from obtaining the application’s source code to
deploying it.

Continuous Delivery: Continuous Delivery is the process of deploying an application into

production servers manually when it has completed testing and the build stages. Here, we’ll
automate the continuous integration processes, however, manual involvement is still required
for deploying it to the production environment.

5. Continuous Monitoring

DevOps lifecycle is incomplete if there was no Continuous Monitoring. Continuous

Monitoring can be achieved with the help of Prometheus and Grafana we can continuously
monitor and can get notified before anything goes wrong with the help of Prometheus we can
gather many performance measures, including CPU and memory utilization, network traffic,
application response times, error rates, and others. Grafana makes it possible to visually
represent and keep track of data from time series, such as CPU and memory utilization.

6. Continuous Feedback

Once the application is released into the market the end users will use the application and
they will give us feedback about the performance of the application and any glitches affecting
the user experience after getting multiple feedback from the end users’ the DevOps team will
analyze the feedbacks given by end users and they will reach out to the developer team tries
to rectify the mistakes they are performed in that piece of code by this we can reduce the
errors or bugs that which we are currently developing and can produce much more effective
results for the end users also we reduce any unnecessary steps to deploy the application.
Continuous Feedback can increase the performance of the application and reduce bugs in the
code making it smooth for end users to use the application.

7. Continuous Operations

We will sustain the higher application uptime by implementing continuous operation, which
will assist us to cut down on the maintenance downtime that will negatively impact end
users’ experiences. More output, lower manufacturing costs, and better quality control are
benefits of continuous operations.

Different Phases of the DevOps Lifecycle

1. Plan: Professionals determine the commercial need and gather end-user opinions
throughout this level. In this step, they design a project plan to optimize business impact and
produce the intended result.

2. Code – During this point, the code is being developed. To simplify the design process, the
developer team employs lifecycle DevOps tools and extensions like Git that assist them in
preventing safety problems and bad coding standards.
 3. Build – After programmers have completed their tasks, they use tools such as Maven and
Gradle to submit the code to the common code source.

4. Test – To assure software integrity, the product is first delivered to the test platform to
execute various sorts of screening such as user acceptability testing, safety testing,
integration checking, speed testing, and so on, utilizing tools such as JUnit, Selenium, etc.

5. Release – At this point, the build is prepared to be deployed in the operational environment.
The DevOps department prepares updates or sends several versions to production when the
build satisfies all checks based on the organizational demands.

6. Deploy – At this point, Infrastructure-as-Code assists in creating the operational

infrastructure and subsequently publishes the build using various DevOps lifecycle tools.

7. Operate – This version is now convenient for users to utilize. With tools including Chef, the
management department take care of server configuration and deployment at this point.

8. Monitor – The DevOps workflow is observed at this level depending on data gathered from
consumer behavior, application efficiency, and other sources. The ability to observe the
complete surroundings aids teams in identifying bottlenecks affecting the production and
operations teams’ performance.

software architecture

Software architecture in DevOps is a framework that integrates the processes, tools, and
teams involved in the software development and delivery lifecycle. It aims to improve the
quality of software delivery and organizational performance.
Key aspects of software architecture in DevOps

 Collaboration

DevOps architecture encourages collaboration between development and operations teams.

  Automation
DevOps architecture uses automation to ensure that changes to code and configuration are
repeatable, traceable, and automated.

  Continuous integration and delivery

DevOps architecture emphasizes continuous integration (CI) and continuous delivery (CD).

  Monitoring
DevOps architecture uses continuous monitoring to identify risks of failure and track the
health of the application.

  Infrastructure as code
DevOps architecture uses software to provision and configure operations.

  Reliability engineer
DevOps architecture includes a reliability engineer on each development team who ensures
that changes are deployed successfully.

Benefits of DevOps architecture

 DevOps architecture can help businesses deliver software more frequently and
consistently.
 DevOps architecture can help businesses address errors more efficiently.
 DevOps architecture can help businesses keep everything functioning seamlessly.

Devops in Software Architecture

 Development and operations both play essential roles in order to deliver applications.
The deployment comprises analyzing the requirements, designing, developing, and
testing of the software components or frameworks.
 The operation consists of the administrative processes, services, and support for the
software. When both the development and operations are combined with
collaborating, then the DevOps architecture is the solution to fix the gap between
deployment and operation terms; therefore, delivery can be faster.
 DevOps architecture is used for the applications hosted on the cloud platform and
large distributed applications. Agile Development is used in the DevOps architecture
so that integration and delivery can be contiguous. When the development and
operations team works separately from each other, then it is time-consuming to
design, test, and deploy. And if the terms are not in sync with each other, then it may
cause a delay in the delivery. So DevOps enables the teams to change their
shortcomings and increases productivity.