An architect's day one job is to know the organization — Each organization is different in its operating model, organization structure, and strategic needs. It’s critical for an architect to understand the current and aspirational state of the organization to be able to make better decisions. In this blog, we will explore some tools that can help architects better understand an…

Value-driven business transformation with hypothesis-driven development — Why Hypothesis Driven Development? Organizations are forced to react to a couple of critical challenges that evolved during the last decade With more and more people connected digitally, most of the new business models are digitally powered. The high volume and velocity of changes in the business landscape make the software requirement itself agile…

A hands-on coding journey to implement ‘Policy As Code’ and validate the fitness of your Kubernetes Application against the cluster policies. —

It was quite a bit learning from different sources to launch my first personal website with Google Kubernetes Engine and Wordpress. It’s worthwhile to document the knowledge for the community to benefit. — Putting across a website end to end with Kubernetes, Google Cloud, and Wordpress involves many moving parts. If you need support in setting up your Wordpress website, feel free to reach me at imarunrk@gmail.com

Let’s start by exploring the API gateway architecture pattern and then slowly deep dive into the details of running a production-grade Kong API gateway. — Generally with many organizations the backend APIs are consumed by multiple front-facing applications like the mobile app, web, and other kiosk applications. In addition to this, many other internal and external integrators may have a need to consume these APIs. We will end up applying some of the below architecture…

Microservices are not the answer to all the problems. It’s the job of an architect, to understand the context and identify the tradeoffs to build a story on monolith vs microservice — In the last 4 years of working with microservices, I have seen a wide range of stories in the path of microservices adoption. While many of these stories are successful ones to celebrate, some of them have really created chaotic situations.

The developers, application/cluster operators, architects, and security team wants to contribute to the Kubernetes YAML continuously to keep the Infrastructure matching to the evolving organization strategy and policy, which demands a workflow. — The software systems we build are always expected to be in a state of dynamic equilibrium. This dynamic equilibrium generally happens in two dimensions a) Fast phased technology changes b) The rapidly evolving business landscape. Artificial Intelligence, Docker, Cloud, Kubernetes, Istio / Other service Mesh, Helm, Microservices architecture pattern, Serverless…

Continuous GitOps, the new age DevOps practice to increase the delivery velocity by achieving an end to end “Git source of truth” with Zero manual changes into the Kubernetes cluster 🏄 — It’s been 10 years now from the time, when we first heard of the word Continuous Delivery. It’s Humble Jez and Farley David talked about Continuous Delivery during 2010 through their book “Continuous Delivery: Reliable Software Releases Through Build, Test and Deployment Automation”. In the last decade, Continuous Delivery has…

Customize the YAML’s to enforce policies from application operators, security operators, and cluster operators. ✊ — Kubernetes let us to declaratively specify our intent on how the applications should be deployed in the underlying infrastructure through YAML. These YAML’s will have application definition, tags needed for governance, tags needed for cross-cutting concerns like logging, application security context definitions, application resource dependencies, etc. The moment we start…