Back to Basics: DevOps

Having been in DevOps (and SRE ) for a bit now, I decided to redo some basic courses.

I found the Fundamentals of DevOps by Michael Forrester ( on KodeKloud ) to be a good, easy but instructive course. It might not blow your socks away but is a productive use of 3 odd hrs.

So if you can, search out the course ( I think it's free on KodeKloud ).

But if you don't have 3 hrs, below is my tl;dr ( tl;dw to be precise ).

****

What is DevOps: It is a perspective that eliminates the barriers between people, processes, and technology so that IT can deliver better, Faster, Secure, and Compliant software for the meeting ( and possibly beating ) business goals.

So it's really about culture, people, mindsets, and processes. Not so much about technology, though that is a very important component.

It's iterative, evolutionary, and about continuous improvements. Embrace 3 perspectives to achieve that.

• Way of the Flow,
• Way of the Feedback
• Continuous Improvement

??

Anti-Patterns in DevOps: It's Not About Tech, It's Not a JOB Title, and Not an End-2-End Framework for all software development.

?

What is Automation:?Application of algorithms, robotics, processes, or Technology to achieve outcomes with minimal human inputs. Anything that you are doing repetitively is a good candidate for automation.

For DevOps, Automation in the below can bring significant rewards in reducing TOIL, enhancing scalability, improving resiliency, improving uptime & availability, and meeting compliance/Industry standards.

• Server Configuration ( IaC ? )
• Code deployment ( CICD )
• Code testing ( Automated test Suites )
• Server Monitoring ( telemetry )

?

The most important part of DevOps is Culture and in that communication ( collaboration & information radiation ).

?

The best measurements to quantify improvements follow a method nicknamed DORA (DevOps Research and Assessment Team).

LT -- Lead time to Deploy/change.?Improved velocity without compromising on quality. Measured as the lag between check-in of new feature to its roll out in Production.

DF -- Deployment frequency. How many times do you deploy per unit time?

CFR -- Change failure rate. Measurement of quality.

MTTR -- Mean time to recovery.

Value of DevOps :

• Builds better and scalable products faster, with higher quality and fewer risks.
• Breaks down barriers between teams, promotes collaboration, and fosters a culture of shared responsibility and trust.
• Improves velocity of delivery.
• Improved telemetry.
• Quantify and qualify data-driven measurements e.g. Change frequency, failure rate, MTTR/MTTD, etc.

?**********

PS : Quite a few good Topologies on: https://web.devopstopologies.com/

?PPS: In DevOps, it is often a small team or even a single person who makes a difference in the culture.

So if no one is with you in the beginning, as (Sir, later renounced ) Tagore said

???? ??? ??? ???? ??? ?? ???

??? ???? ??? ??

?"If no one responds to your call, then go your own way alone", ( From Wiki Page?)

?Or on the same lines from Majrooh Sultanpuri

??? ????? ?? ??? ?? ?????-?-?????? ???

??? ??? ??? ?? ?? ?????? ???? ???

( Very ) Loosely translated "I started alone on my journey, people joined and group/momentum was formed".

#sre #devops #devopscommunity #devopsculture