GitOps Introduction

DevOps has become a digital transformation strategy for many organizations. It's about software development and operations teams working together and engineering and automating their practices. This will lead to writing code for small changes and testing and implementing those small changes very quickly. This was an amazing step forward and wonderful software practice.

GitOps, The next generation infrastructure

Automation and Orchestration had become the focus for DevOps culture. 

Bringing automation to a company isn't an easy task; it requires coordination among teams and changing how we understand and interact with the application lifecycle. 

DevOps: Driving Innovation With Old Habits

DevOps can help drive cost-efficiency, greater productivity and innovation

When software development and IT operations merge and work in a state of harmony, they create a flow that we call continuous product delivery. Ideal for project managers, this flow is the elixir to innovation and enables the agility needed to respond to changing market requirements. It also creates currents of speed, proactiveness and integration within enterprises. However, asynchronous code updates, inadequate IT infrastructure, siloed functioning and inefficient processes can hinder this flow.

Chaos Engineering :D

is the discipline of experimenting on a system in order to build confidence in the system’s capability to withstand turbulent conditions in production.

Has DevOps morphed into ITSM?

The more that DevOps matures, the more it looks like IT service management (ITSM).

What? For some time, DevOps has been challenging the old ways of doing ITSM. DevOps has been shifting the traditional ITSM mindset from one of "control" to one of "enablement."

But the disciplines are increasingly merging. Here's why and how.

DevOps Metrics and Key Performance Indicators

When tracking key DevOps metrics, focus less on the perceived success or failure according to any one indicator, but rather, on the story these metrics tell when examined together. A result that seems problematic on its own could look completely different when analyzed alongside additional data.


Careful tracking of the KPIs highlighted bellow can ensure not only greater efficiency in development and production, but more importantly, the best possible end-user experience. Embrace DevOps metrics, and you could see vast improvements in application deployment and feedback.

Using DevOps Metrics Effectively

If you’re a DevOps leader, you have a very tough job. You have to radically transform processes and behaviors that have been ingrained in IT for decades. You have to adopt new technologies quickly while still delivering code quickly and cost-efficiently. And you have to do all this better than your peers at other companies. Otherwise, you’ll simply slow your company’s progress in the new digital marketplace while your better-performing competitors gain advantage.

DevOps & KPIs is making an impact?

DevOps encourages incremental changes and faster releases while also improving quality and satisfaction. But how do we know if DevOps is making an impact? How do we decide what needs to change? We need to measure and this is where DevOps metrics come in.

DevOps Metrics and KPIs

DevOps may seem like the new kid on the block with all the buzz surrounding it, but it’s actually been around for a while and has proven itself a valuable method for improving software enterprises’ ability to deliver better products in less time. It achieves this lofty goal by leveraging the power of cross-discipline teams and empowering transparent communication throughout the organizations. A culture of communication goes a long way in improving morale as well as efficiency.

Gitflow & Gitflow Workflow

GitFlow is one of the popular branching strategies if you using Git version control. Most of the teams I have worked with generally are very satisfied using it. With fixed branch names, pull requests for code reviews, teams find that it fits very nicely with their day to day workflow. 

Gitflow Workflow is a Git workflow design that was first published and made popular by Vincent Driessen at nvie. The Gitflow Workflow defines a strict branching model designed around the project release. This provides a robust framework for managing larger projects.  

How BDD and Continuous Delivery Help Developers Maintain Flow

Programming is cognitive work, and programmers perform their best work under intense concentration. While there are external factors that can affect this, such as having a quiet office, controllable ways of communication, etc., there are also some internal factors that need to be taken into account. In fact, the way we work can influence the quality of the outcome the most.

Docker Image Size – Does It Matter?

Does Docker image size matter? The answer I usually hear is “yes”.
The logical question that follows is “why?”.

I’ve heard the following two answers too often for my liking:

Continuous Delivery Patterns with Serverless Applications

Serverless is a new paradigm in which we need to neither administer nor scale the servers that run our code. The promise is that much less operations work is needed to deliver value to customers.

The catch is that the unit of code deployment is now a function, not an application of arbitrary complexity. Deployment also includes configuring managed services and infrastructure to which functions connect. This means that new tools and practices are needed to achieve optimal developer productivity, which, as always, revolves around being able to move fast. Here’s how this is achieved:

7 Ways Continuous Delivery Helps Build a Culture of Learning

At the heart of continuous delivery is a fast feedback loop that immediately shows developers the effects of their work. Mistakes are found and fixed quickly, while beneficial changes can be released and deployed to customers without having to wait for a distant future release date. This rapid feedback helps build an organizational culture of learning and responsibility.

Elements of a Continuous Deployment Workflow

Continuous delivery is a broad set of software development practices designed to ensure that every change is rapidly deployable to production, while the system performs its business function uninterrupted and as intended.

CI/CD principles

CI/CD enables the best tech companies to improve their products many times per day. Here’s what you need to know to do the same.

Why We Need Continuous Integration

The Problem
First, we will take a look at the source of the problem, which lies in the software development cycle. Next, we will cover some of the change conflicts that can take place during that process, and finally we will explore the main factors that can make these problems escalate, followed by an explanation of how continuous integration solves these issues.

What’s the Difference Between Continuous Integration, Continuous Deployment and Continuous Delivery?

Continuous integration, continuous deployment, and continuous delivery are like vectors that have the same direction, but different magnitude. Their goal is the same: make our software development and release process faster and more robust.

Continuous Integration (CI) Explained

Continuous integration enables iterative software development, reduces risks from defects and makes developers highly productive.

What is Continuous Integration?
Continuous integration (CI) is a software development practice in which developers merge their changes to the main branch many times per day. Each merge triggers an automated code build and test sequence, which ideally runs in less than 10 minutes. A successful CI build may lead to further stages of continuous delivery.

CI/CD Pipeline: A Gentle Introduction

Do you want your engineering team to deliver bug-free code at high velocity? A fast and reliable CI/CD pipeline is crucial for doing that sustainably over time.

What is a CI/CD pipeline?
A CI/CD pipeline helps you automate steps in your software delivery process, such as initiating code builds, running automated tests, and deploying to a staging or production environment. Automated pipelines remove manual errors, provide standardized development feedback loops and enable fast product iterations.