Exploring Cloud-Native Innovations: A Weekly Overview
Written on
Introduction to Cloud-Native Concepts
In this week's edition, I aimed to present some foundational articles that will lay the groundwork for key concepts currently shaping the cloud-native landscape and will remain significant in the future.
We will kick off with an overview of managing substantial workloads in Kubernetes through the widely recognized package manager for cloud-native applications, Helm. This will give you a clear understanding of how to implement it within your cluster.
Next, we will delve into the transformative GitOps methodology, examining its implications across various roles, including developers, throughout its adoption journey.
To conclude, we will review an article that discusses the most prevalent protocols used today for exposing synchronous services (REST, GraphQL, and gRPC), enabling you to grasp the unique features of each and their appropriate use cases.
Understanding Helm 3
What:
This article introduces Helm, the package manager for Kubernetes, highlighting the significant changes in its latest major version, Helm 3, which presents a distinct architectural approach compared to its predecessor.
Why:
Helm's importance in Kubernetes management is growing, akin to how package managers are vital in Linux distributions. When deploying workloads with interconnected components and a variety of resources (such as configmaps, secrets, deployments, and daemon sets), having a higher-level tool is crucial for both deployment and ongoing maintenance of the entire stack.
The Significance of GitOps for Developers
What:
This piece provides an introduction to GitOps, emphasizing its relevance for IT professionals, particularly developers. GitOps represents a paradigm shift in managing infrastructure alongside application code, evolving from Infrastructure as Code (IaC) and detailing the tools available for its implementation.
Why:
As noted, GitOps is the evolution following Infrastructure as Code. It facilitates comprehensive environment management, allowing easy replication and the ability to revert to previous states, similar to code management. Its adoption is on the rise within enterprises, positioning it as a major trend in the coming years.
When to Choose Between REST, gRPC, and GraphQL
What:
This article offers an in-depth analysis of the three leading technologies for service exposure: REST, gRPC, and GraphQL. It evaluates the advantages and disadvantages of each and clarifies in which contexts one technology might be preferable over the others.
Why:
We have transitioned from a period where REST was the sole option for service exposure. Following the era of SOAP, we entered a REST/JSON dominance. Now, we are moving towards a diverse landscape for synchronous services. It is essential to stay informed about the appropriate scenarios for employing each technology as we adopt a "best tool for the job" mindset.
Quote
"The way to get started is to quit talking and begin doing."
— Walt Disney