Azure Kubernetes Service (AKS) with Terraform deployment

AKS components I assumed that you are familiar with the Kubernetes Cluster concepts (elementary level). Therefore I didn’t do any deep dive into the elementary components. The focus of this post is the following topics: The control plane (Kubernetes core component) It’s the core of the Kubernetes Cluster and doesn’t matter on which cloud providerContinue reading “Azure Kubernetes Service (AKS) with Terraform deployment”

Azure Arc enabled Kubernetes

Introduction What does “Arc-enabled Kubernetes” mean? it means a Kubernetes Cluster that the Azure Arc Agent has been installed on. Should an instance of Azure Arc be provisioned? No, Azure Arc is a global service. What about data security? very good question! I’ll explain it below. Because first, you have to know how Azure ArcContinue reading “Azure Arc enabled Kubernetes”

Azure Identity & Access Managemen

Introduction As we know Microsoft Azure Cloud platform works seamlessly with Azure Active Directory (AAD). The following products are three of many cloud-based Microsoft products. As demonstrated below each of them has its own RBAC. But only AAD manages the identities and the Azure Subscription & Azure DevOps and also the other products which canContinue reading “Azure Identity & Access Managemen”

Multi-Cloud

Introduction This document gives us the definition of different cloud classifications and focuses on the Multicloud and Hybrid cloud and the organization’s tendency to adapt to the cloud specially for multi-cloud. This document even refers to the challenges of multi-cloud at the management and technical level and the reasons of them, and in the lastContinue reading “Multi-Cloud”

ITIL

IT Service/ Management Stakeholders of IT services Value and outcomes Value is the perceived benefit, usefulness, or importance of something to a stakeholder. The value of a service is what the customer seeks. The value has subjective quality. The value definition is different in ITIL V3 and V4. Outcome is the result for a stakeholderContinue reading “ITIL”

Pipe and Filter Design Pattern

Break up logic in small steps instead of a long-run service or process. Approach Each request must call services separately instead of a long-running service. Data is passed from one filter to another filter. Filters exchange data use a standardized format and protocol. Why filter data must be standardized? We can add or remove filtersContinue reading “Pipe and Filter Design Pattern”

Throttling Design Pattern

Knows as Rate Limiting. We place a throttle in front of the target service or process to control control the rate of the invocations or data flow into the target. We can use the cloud services to apply this design pattern. This can be useful if we have an old system and we don’t wantContinue reading “Throttling Design Pattern”