DevOps and methodologies 1 introduction

Software monitoring and logging. Once software is moved to production, it must be monitored to ensure stable performance and increased customer satisfaction. This stage also involves performance analysis and logging, raising smart alerts on various issues, gathering customer feedback, and so on. Tools for performing these tasks include Prometheus, Grafana, Elastic (ELK) Stack, Splunk, and Sumo Logic.


Methodologies, principles and strategies
DevOps is related to Agile software program development due to the fact Agile practitioners promoted DevOps as a way to extend the methodology into manufacturing. The approach has even been labeled a counterculture to the IT carrier control practices championed in ITIL. DevOps does no longer have an legitimate framework.
To hone their strategies, groups should recognize the associated contexts of DevOps, Agile and Waterfall development, web site reliability engineering (SRE) and SysOps, and even the variations within DevOps.
Waterfall vs. DevOps development
In a linear path to production, waterfall development consists of a succession of steps and gates. Requirements, analysis, design, coding and implementation, testing, operation and deployment, and maintenance are the phases involved. Waterfall teams test new code in an isolated environment for quality assurance (QA) before releasing it to operations for use in production if all requirements are met. Multiple releases are deployed at simultaneously, with rigorous controls. Operations is in charge of support. Long delays between software releases are common with waterfall techniques. Developers are not always aware of operational bottlenecks that prevent code from working as expected because development and operations teams work independently.With fewer gates and a more continuous workflow, the DevOps model aligns development, QA, and IT operations tasks. Some of the operations team's tasks, for example, transfer to the development team as the app delivery pipeline progresses. IT operations gives code improvement feedback. DevOps relies on continuous development, continuous integration, continuous delivery, and continuous monitoring processes rather than gated phases.
Agile vs. DevOps development
The Agile Manifesto defines Agile as a software development methodology. Agile teams focus on sprints, which are incremental and rapid cycles of code production and delivery. Each sprint builds on the previous one, making the program extremely responsive to changing requirements. Through this cycle, it is possible for a project's original concept to be lost.
DevOps originated from Agile's success in speeding up development and the awareness that disconnects between development and operations teams, as well as between IT and the business side of the organization, hampered Agile software delivery to customers significantly.
Development and operations teams have independent objectives and leadership in an Agile-only workflow. Both development and operations teams handle code throughout the software development lifecycle when a firm employs DevOps and Agile together. While Agile work is sometimes codified through frameworks such as Scrum, DevOps does not.
SRE vs. DevOps
Site reliability engineering emerged at the same time as Agile and DevOps. It is essentially a programming- and automation-focused approach to the software development lifecycle that was started in the early 2000s at Google. Problems should be addressed in a manner that is preventing them from happening continuously. Rote tasks are needed to be minimized.
SysOps vs. DevOps
An IT administrator or team managing production deployment and support for a large distributed program, such as a SaaS offering, is known as SysOps. SysOps teams, like DevOps adopters, should be familiar with cloud computing and automation, as well as other technologies that allow programs to scale well. IT outages and events are troubleshooted by SysOps teams, who also monitor for performance issues, enforce security regulations, and optimize operations.
They, like other IT administrators, are concerned with high availability, fault tolerance, security, and performance. While SysOps specialists are likely to utilize some development tools and be familiar with development processes, their work is not as closely linked to development as a DevOps job. Within DevOps, however, SysOps roles might exist.

BizDevOps vs. GitOps vs. DevSecOps
DevOps is sometimes broadened to encompass other jobs or divisions in some businesses. Security planning, scans, testing, and reviews take place continually throughout the DevOps loop in DevSecOps. Executives, application owners, and other business stakeholders are connected to the technical team that builds, tests, and supports software through BizDevOps. While it is arguable that more collaboration is preferable to fewer, these collaborators must provide effective, timely, and exact input.
GitOps is a variant of DevOps or a separate faction within the same movement. GitOps advocates declarative source control over application and infrastructure code, and is named after the eponymous repository and version control system. Everything about the software comes from a single source of truth, from feature needs to deployment environment.