Tu resumen semanal de lo que encontré más relevante en el ecosistema nativo de la nube.
Resumen
En esta edición, decidí traer algunos artículos introductorios para proporcionar la base de conceptos importantes en la industria ahora, pero también que seguirán siendo relevantes en el futuro próximo.
Comenzaremos hablando sobre la gestión y operación de grandes cargas de trabajo en Kubernetes con el uso del conocido gestor de paquetes para cargas de trabajo nativas de la nube, Helm, donde tendrás una gran visión de qué es y cómo empezar a usarlo en tu clúster.
Continuaremos con uno de los cambios de juego en la gestión de operaciones e infraestructura, como el movimiento GitOps, y veremos cómo esto impactará en todo tipo de roles, incluso en los desarrolladores en su camino.
Y terminaremos con un artículo que cubre los protocolos más utilizados hoy en día para exponer servicios sincrónicos (REST, GraphQL y gRPC) para que puedas conocer las características de cada uno de ellos y dónde usar uno u otro.
Historias
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.
Cita
La forma de empezar es dejar de hablar y comenzar a hacer.
Walt Disney