Photo by Chronis Yan on Unsplash

Infrastructural Maturity and Return of Investment (ROI) with Containerization

Many organizations have their own model on what they determine as “Infrastructural Maturity”. However, they never identify and describe what this looks like. These organizations do not describe how to do this by using actual technology. Instead, they utilize buzz words that track marketing. Some of these words include containerization, DevSecOps, GitOps, Scalability, Availability, and Value Stream Mapping. The truth about Infrastructural Maturity is that it is unique to every organization. The key factor is that “Governance” controls the very speed at which technology is delivered to the customer. Every organization has its own set of Governance. Another factor to consider is budget. Budget changes the way infrastructure is delivered or even the change management of that delivery. This article will talk about the basic category for Infrastructural Maturity, identify governance and how to mitigate with a “Shift Left” approach, and how an organization will deliver based on budget. In the end, this article will cover how these affect the Return of Investment (ROI).

The basics categories for Infrastructural Maturity are:

Manual & Domain Centric Infrastructure

This phase describes the infrastructure which requires a higher level of oversite and integration. These infrastructures can include:

Automated Provisioning (IaC) with Implied Configuration as Code (CaC)

Now your teams are starting to realize the power of Infrastructure as Code (IaC) and Configuration as Code (CaC). These two can make the world of Configuration Management happy. This area can range from On-Prem, Hybrid, Cloud Native, to the Internet of Things (IoT) approaches. We have to remember that things in the cloud reside on something as well.

This infrastructure category can include:

Decoupled Infrastructures

Provisioning infrastructures and continuously updating them with CaC is one thing, but another is decoupling it. Decoupling allows the capability of an organization to remove “Vendor lock-in”. What is vendor lock-in? This is when an organization specifically identifies a product to be the complete solution for all its delivery needs. Technical debt is included as components for the Software as a Service (SaaS) are de-supported or changed. Changes within a SaaS can cause a required involuntary change to the objectives of a product that increases the time to market.

This infrastructure category can include:

Cloud-Native Approaches for Both Cloud Service Providers and On-Prem

Cloud-native can be misinterpreted for containing an infrastructure within a Cloud Service Provider (CSP). Most common CSPs of Amazon Web Services, Google Cloud Platform, or Azure. However, Cloud Native architectures can reside on On-Prem systems. Basically an On-Prem system with a container and functions as a service orchestration system.

This infrastructure category can include:

Services on Demand with Implied Base Models

As infrastructures mature so does the capability of determining when services should be rendered or not. The world of microservices is ever-increasing but so does the cost if left unmitigated. That is where this infrastructural maturity comes in. As infrastructure, they can completely build-up to full infrastructures for services in minutes. This can be done with cloud functions such as Lambda on AWS to quickly execute code to provide to the customer.

This infrastructure category can include:

Enterprise Solution Architect | Certified Kubernetes Administrator ⚓ | SAFe SPC | LeSS Practioner | AWS Solutions Architect | Dev*Ops/GitOps Engineer 🔥

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store