HTML to Markdown
YouTube
Convent Text

In this podcast, Michelle Noorali, senior software engineer at Microsoft, sat down with InfoQ podcast co-host Daniel Bryant. Topics discussed included: the service mesh interface (SMI) spec, the open service mesh (OSM) project, and the future of application development on Kubernetes.
​

Key Takeaways

​

• The service mesh interface (SMI) specification provides a standard interface for service meshes on Kubernetes. SMI includes definitions for traffic management, traffic policy, and traffic telemetry.
• The SMI spec is aimed at both platform builders/operators and application developers. Platform operators can provide sensible service-to-service communication defaults, and developers can specify service/application release configuration, such as canary releases.
• Open Service Mesh (OSM) is a lightweight and extensible cloud native service mesh. Using the CNCF Envoy project. OSM implements SMI with the primary goals of securing and managing microservice applications.
• A common use case for adopting service mesh technology is to enable transport security and verification of service-based identities (e.g. via mTLS and SPIFFE).
• Although functionality provided by a service mesh will most likely not be added to the core Kubernetes project, it is likely that service mesh implementations will be provided within Kubernetes distributions (distros).

#observability #service mesh #microservices #kubernetes #architecture & design