smi-sdk-go
Service Mesh Interface SDK for Go (by servicemeshinterface)
smi-spec
Service Mesh Interface (by servicemeshinterface)
smi-sdk-go | smi-spec | |
---|---|---|
1 | 12 | |
66 | 1,047 | |
- | - | |
0.0 | 2.7 | |
almost 3 years ago | 7 months ago | |
Go | Makefile | |
Apache License 2.0 | Apache License 2.0 |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
smi-sdk-go
Posts with mentions or reviews of smi-sdk-go.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-05-02.
-
Service Mesh Interface
Features(document) Feature(implement) Crds Source-code Description Traffic policy traffic access access.smi-spec.io v1alpha3 https://github.com/servicemeshinterface/smi-sdk-go/tree/main/pkg/apis/access Apply policies like identity and transport encryption across services Traffic telemetry traffic metrics metrics.smi-spec.io v1alpha2 https://github.com/servicemeshinterface/smi-sdk-go/tree/main/pkg/apis/metrics Capture key metrics like error rate and latency between services Traffic management traffic split split.smi-spec.io v1alpha4 https://github.com/servicemeshinterface/smi-sdk-go/tree/main/pkg/apis/split Shift traffic between different services
smi-spec
Posts with mentions or reviews of smi-spec.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-06-08.
-
A Comprehensive Guide to API Gateways, Kubernetes Gateways, and Service Meshes
The Service Mesh Interface (SMI) specification was created to solve this portability issue.
-
Service Mesh Use Cases
> I suspect if a Service Mesh is ultimately shown to have broad value, one will make it's way into the K8S core
I'm not so sure. I suspect it'll follow the same roadmap as Gateway API, which it already kind of is with the Service Mesh Interface (https://smi-spec.io/)
-
Service Mesh Considerations
It is very common that a service mesh deploys a control plane and a data plane. The control plane does what you might expect; it controls the service mesh and gives you the ability to interact with it. Many service meshes implement the Service Mesh Interface (SMI) which is an API specification to standardize the way cluster operators interact with and implement features.
-
Kubernetes: Cross-cluster traffic scheduling - Access control
Before we start, let's review the SMI Access Control Specification. There are two forms of traffic policies in osm-edge: Permissive Mode and Traffic Policy Mode. The former allows services in the mesh to access each other, while the latter requires the provision of the appropriate traffic policy to be accessible.
-
Announcing osm-edge 1.1: ARM support and more
osm-edge is a simple, complete, and standalone service mesh and ships out-of-the-box with all the necessary components to deploy a complete service mesh. As a lightweight and SMI-compatible Service Mesh, osm-edge is designed to be intuitive and scalable.
- KubeCon 2022 - Jour 1
-
Kubernetes State Of The Union — KubeCon 2019, San Diego
I started on Monday, attending ServiceMeshCon2019. My guesstimate is that about 1000 people attended it. I believe Service Mesh is playing such a crucial role in scaling cloud native technologies that large scale cloud-native deployments may not be possible without service mesh. Just like you cannot really succeed in deploying a microservices based application without a microservices orchestration engine, like Kubernetes, you cannot scale the size and capacity of a microservices-based application without service mesh. That’s what makes it so compelling to see all the service mesh creators — Istio, Linkerd, Consul, Kuma — and listen to them. There was also a lot of discussion of SMI (Service Mesh Interface) — a common interface among all services mesh. The panel at the end of the day included all the major service mesh players, and some very thought provoking questions were asked and answered by the panel.
-
GraphQL - Usecase and Architecture
Do you need a Service Mesh?
-
Introducing the Cloud Native Compute Foundation (CNCF)
In the episode with Annie, she gave a great overview of the CNCF and a handful of projects that she's excited about. Those include Helm, Linkerd, Kudo, Keda and Artifact Hub. I gave a bonus example of the Service Mesh Interface project.
-
Service Mesh Interface
SMI official website: https://smi-spec.io
What are some alternatives?
When comparing smi-sdk-go and smi-spec you can also consider the following projects:
go-hubspot - A fully-featured OpenAPI generated HubSpot client for Go
cni - Container Network Interface - networking for Linux containers