Your Weekly Summary of What I Found More Relevant in the Cloud-Native Ecosystem.
Summary
On this issue, I decided to bring some introductory articles to provide the foundation of important concepts in the industry now but also that it will continue to be relevant in the upcoming future.
We will start by talking about managing and operationg big workloads in Kubernetes with the use of the well-known package manager for cloud-native workloads Helm, where you will have a great view on what is and how start using it in your cluster.
We will continue with one of the game changer in the operation and infrastructure managmenet such as the GitOps movement and see how this will impact all different kind of roles even developers on its journey.
And we will end with one articles covering the most used protocols today to expose synchronous services (REST, GraphQL and gRPC) so you can know the characteristics of each of them and where to use one or the other.
Stories
This post is an introduction to the Kubernetes Package Manager Helm. It especially covers its changes in the latest major release, Helm 3, that has a big change in the architecture comparing with the previous version.
Helm is becoming more and more important in the managing of kubernetes at the same level that package manager are important in Linux distribution. When we have the deploy workloads that have different componentes related to each other and a set of resources (configmaps, secrets, deployments, secrets, daemon sets.. etc) it is important to have one level up to keep it all together not only for deployemnt purposes but especially for maintenance and operation of this stack.
This post is an introduction to GitOps and why this is relevant for any people related to IT but with a focus on how this will impact the developers. GitOps is the movement to manage infrastructure at the same level you manage the code of your application. It is the next step after Infrastracture as a Code (IaC) and it is covered from a technical and practice perspective with the tools you can use to implement this approach
As discussed GitOps is the next step after Infrastructure as a Code and allow us to have a complete management of the environment being able not only to replicate it easily but also to rollback to any point in the past as you can do with any of the code you develop yourself. It is starting to be adopted by enterprises and it will be one of the next big things for the upcoming years
Second part of this great analysis on the three leading technologies to expose our services to be invoked from consumers: REST, gRPC, GraphQL. It focus on the pros and cons of each of the technology and more important in which scenarios one of this technologies is more useful than the others.
We have lived a time when the only way to expose your services was REST. After the rule of SOAP we entered into a REST/JSON kingdom but now we are coming again to a heterogeneous situation also covering the synchronous services and that’s why we need to be informed and know in which scenarios we should use one technology or the other, because now everything is moving under the “best tool for the job” kind of approach and we need to be ready for that.
Quote
The way to get started is to quit talking and begin doing.
Walt Disney