GitFlow: Branching strategy for Git

  Today, I am publishing from a very old document (I created and published in 2017) on Branching strategy for Git (can be applied on other as well). This branching model is also known as GitFlow and is very powerful for scalability needs. 1. Source Code Configuration Management GIT is a distributed version control system that gives team members a wide flexibility in how they use version control to share and manage code. However, we need a balance between this flexibility and the need to collaborate and share code in a consistent manner. Team members publish, share, review, and iterate

Continue reading

Pi-Hole: The sentry at your doorstep

Sorry for writing after such a long time. My R&D pipeline almost dried at the right end while the left end is overflowing. The backlog is getting longer. I promise to start improving my presence over time. So, won’t you like to have sentry at your doorstep to shoo away the bad elements or the unwanted guests? Definitely yes. This is equally important for your digital doorway as well. This is even more relevant as you have started working from home. Everyone at home are now working online and a whole lot of browsing and a whole lot of extra

Continue reading

Microservices – Panacea or just another pattern?

Microservices is the keyword these days. And it is solving many problems, helping applications become agile and the support team getting better sleep. But, as it is catching the fire, it also raised eyebrows – is it necessary to have microservices in my application? The other day, I faced this question from such an angle. And, here I want to express my thoughts and experiences with microservices. First, let us accept that Microservices is just another design pattern. Each design pattern has a scope and is actually a path or approach to the solution to a design problem. So, microservices

Continue reading

Why Shift Left? And how much?

The new mantra in town – “Shift Left“. So we wish to shift everything to left (except in the case of right-to-left, we shall do it otherwise). This is called the mantra of DevOps. Left of what? The delivery pipeline. The great thing that we often call CI/CD in the vocabulary of DevOps. The primary concept of DevOps is to reduce friction in the pipeline and enable early feedback to the stakeholders. This is more relevant when the team is using Agile process or methodology. It started with builds shifting left to have early feedback for success of a build.

Continue reading