Modern, cloud-native infrastructure can be created and destroyed within minutes. It can be scaled up and down depending on load and usage patterns.
Infrastructure as Code (IaC) is a common pattern where virtualized infrastructure and auxiliary services can be managed using configuration expressed in almost any language, usually hosted in a source code repository.
IaC enables automated, repeatable and reliable creation and maintenance of any virtualized infrastructure. If you are interested to learn more about available tools and practices, here is a list to get you started:
Terraform, Pulumi and Crossplane all support multiple providers and are great for operating…
This is the second part of a mini-series centered around cloud computing; a high-level overview of vendor lock-in and mitigation strategies.
Part 1: Introduction to cloud computing
Part 2: Vendor lock-in — this blog
Vendor lock-in happens when a customer is dependent on a vendor’s products or services and is unable to switch to another vendor without incurring substantial costs and/or organizational changes. This generic definition applies also to cloud vendor lock-in where cloud vendor is any public cloud provider like Azure, AWS, GCP, Hetzner, Linode, etc.
Cloud vendors aim to be a one-stop-shop where customers can fulfill all their…
Cloud computing, cloud native, public cloud, private cloud, hybrid cloud, multi cloud, Azure, AWS, GCP, IBM, Linode, Alibaba, FaaS, CaaS, SaaS, PaaS, IaaS, DaaS… confused already? In this blog series, we will try to bring some clarity to those topics.
What are the methods and decision process around selecting appropriate cloud computing setup to best fulfill our requirements? Each blog in the series will be centered around specific requirement and using industry best practices will propose a suitable solutions.
Let’s start by defining our vocabulary around cloud related concepts which will be useful later in our analysis. …
In this blog we will focus on software documentation, namely the documentation produced by teams and individuals involved in defining and developing software (architects and developers). There are other complementing types of documentation like requirements, business analysis, etc which we will not be focusing on.
How many times we jump into an existing active project or take on maintenance of “legacy” software, only to find out that documentation is either missing or not sufficient.
This is unfortunately a very common experience for many development teams. Why is this happening? There are a few reasons:
This is the fifth part of Kubernetes mini-series Kubernetes explained deep enough
For web version of this blog and more information about docker, Kubernetes and Docker Certification, please visit:
Part 2: Kubernetes explained deep enough: Storage
Part 3: Kubernetes explained deep enough: Deployments
Part 4: Kubernetes explained deep enough: Configuration
Part 5: Services discoverability, DNS, cluster communication — this blog
This blog is a little bit longer than other parts of Kubernetes explained deep enough. Kubernetes networking is a very complex topic and trying to write about all nuances of different services and mechanisms would probably take…
This is the fourth part of Kubernetes mini-series Kubernetes explained deep enough
For web version of this blog and more information about docker, Kubernetes and Docker Certification, please visit:
Part 2: Kubernetes explained deep enough: Storage
Part 3: Kubernetes explained deep enough: Deployments
Part 4: Kubernetes explained deep enough: Configuration — this blog
Part 5: Services discoverability, DNS, cluster communication
Visit Kubernetes documentation if you need a refresher about Configuration
Basic definitions are provided on diagrams below
Kubernetes natively supports 2 resources geared towards storing configuration consumed by pods. …
This is the third part of Kubernetes mini-series Kubernetes explained deep enough
For web version of this blog and more information about docker, Kubernetes and Docker Certification, please visit:
Part 2: Kubernetes explained deep enough: Storage
Part3: Kubernetes explained deep enough: Deployments — this blog
Part 4: Kubernetes explained deep enough: Configuration
Part 5: Services discoverability, DNS, cluster communication
Visit Kubernetes documentation if you need a refresher about Deployments
Basic definitions are provided on diagrams below
Typical deployment resource consists of following objects:
Part 2: Persistent Volumes and Persistent Volume Claims
This is the second part of Kubernetes mini-series Kubernetes explained deep enough
For web version of this blog and more information about docker, Kubernetes and Docker Certification, please visit:
Part 2: Kubernetes explained deep enough: Storage — this blog
Part3: Kubernetes explained deep enough: Deployments
Part 4: Kubernetes explained deep enough: Configuration
Part 5: Services discoverability, DNS, cluster communication
Visit Kubernetes documentation if you need a refresher about Persistent Volumes and Persistent Volume Claims
Basic definitions are provided on diagram below
Cluster admin creates persistent volumes as cluster resources…
Part 1: Introduction — this blog
Part 2: Kubernetes explained deep enough: Storage
Part3: Kubernetes explained deep enough: Deployments
Part 4: Kubernetes explained deep enough: Configuration
Part 5: Services discoverability, DNS, cluster communication
For web version of this blog and more information about docker, Kubernetes and Docker Certification, please visit:
As the popularity of Kubernetes grows, so does the number of great online resources and learning materials. A lot of available information is either designed for absolute beginners or does a very deep dive into a specific topic.
My goal is to write about Kubernetes topics in a practical way…
Containers are now a mature solution providing an additional level of infrastructure abstraction. In many cases, containers can replace workloads traditionally powered by virtual machines.
In this blog, we are going to look at Azure Container Instances and showcase how fast and easy it is to deploy containers directly from your docker CLI to Azure.
If you would like to follow along, you will need to have Azure subscription, Azure CLI and Docker Desktop instance.
Azure Container Instances is a compute offering that bridges the gap between lightweight Azure Functions…
Opinions: Multi-cloud is real, Microservices are hard, Kubernetes is the future, CLIs are good. Me: Love jogging with my dog and learning new things.