This talk explains, in simple and straightforward Spanish, the difference between the Sidecar model and the model without Sidecar.
For Service Meshes, the Sidecar model was the only viable way to ensure that the mesh could take control of the application network.
With the evolution of Kubernetes, that assertion has become obsolete.
Today, Istio Service Mesh has brought the alternative. An architecture that reduces the amount of resources needed to make the mesh possible and eliminates the feeling that Istio is there.
With Istio Ambient Mesh, the user implementing a workload in Kubernetes does not notice that the application is part of a mesh.
It is completely transparent.
Key conclusions:
- Concept of service mesh.
- Concept of Sidecar.
- Concept of Sidecar-less.
- Sidecar-less component (Istio Ambient Mesh).
** This event was held in Spanish**
