Your Weekly Summary of What I Found More Relevant in the Cloud-Native Ecosystem.
On this issue, I decided to include the articles that impacted me the most, and at the same time, I think it can provide great content to you if you come with me on this journey.
We will start by talking about the critical concepts at the core of the container world and how to stop letting the word Docker confuse us all to refer to different components and projects.
We will continue with one of the essential standards for the near future, such as OpenTelemetry, the way to go since today to enable an interoperable distributed tracing strategy.
And we will end with one of the ways to shift left security in our processes by including security and other kinds of checks even before the code reach the repository.
This article covers all the definitions that are relevant in the containerization world. Especially when we try to name everything as docker, Benjamin will help us understand the different objects from the Docker project, the evolution of the alternatives, and the current state in a Kubernetes environment.
The article is very relevant because this misunderstanding about the different components required when we run a container in a Kubernetes environment generates additional noise, as we have seen in the past, and a lot of confusion in the industry itself. So this is a must-read to start calling this for the right name.
This article covers the principles of the OpenTelemetry project but with a practical approach using a demo to highlight the benefits and the key concepts for this new standard created by the join of the OpenCensus and OpenTracing projects to provide a common way to handle distributed traces.
Observability is one of the key concepts we need to keep in mind when creating our cloud-native architectures. In addition, we must back standards to simplify the interoperability of the different technologies to encourage the polyglot approach and “use the right tool for the right job” philosophy. So if you are not in this world jet, let Ramon and John introduce it to you with this great demo.
The article covers how the pre-commit tool will help us perform several tasks before the developers commit their code to the repository to ensure many good practices are in place.
This topic is very relevant because it will encourage the shift-left movement raised for the DevSecOps practices to include security practices and checks in the early phases of the development to ensure that the code we create is deployed faster and more secure it was in the past.
The greatest glory in living lies not in never falling, but in rising every time we fall.Nelson Mandela