Announcing Service Mesh Interface (SMI) Support and Collaboration

Announcing Service Mesh Interface (SMI) Support and Collaboration

  • May 25, 2019
Table of Contents

Announcing Service Mesh Interface (SMI) Support and Collaboration

Today we announced that Solo.io is a launch partner of the Service Mesh Interface (SMI) specification in collaboration with Microsoft, Bouyant and Hashicorp with support across the cloud-native ecosystem. As part of today’s announcement, the SuperGloo project and The Service Mesh Hub are the first reference implementations of SMI available today. The Service Mesh Interface (SMI) is a specification for service meshes that run on Kubernetes and defines a common standard that can be implemented by a variety of providers.

This enables the industry to innovate rapidly while preserving a great end user experience. A recent blog post by Christian Posta talked about how this need is greater as adoption and innovation start to gain momentum and we are excited to see the industry converging on SMI. We started this journey last year with the open source launch of SuperGloo for mesh-agnostic orchestration to unify and automate the management lifecycle.

Last week we continued down this path and launched the Service Mesh Hub focusing on the end user experience and the collaboration and innovation in the ecosystem. As of today’s announcement, both SuperGloo and Service Mesh Hub have been updated and are the first reference implementations of the SMI specification.

Source: medium.com

Tags :
Share :
comments powered by Disqus

Related Posts

Knative and Solo.io Gloo

Knative and Solo.io Gloo

Knative is talked about a great deal, especially around how its capabilities can help provide more standard building blocks on top of Kubernetes for building microservices and serverless like services, e.g., scale to zero, and scale on demand. Knative high level has three capability areas: building, serving, and eventing. This post will provide some examples around Knative Build and Knative Serving with Solo.io Gloo.

Read More
AWS App Mesh—Service Mesh for Microservices Running on AWS

AWS App Mesh—Service Mesh for Microservices Running on AWS

The idea of a “service mesh” has become increasingly popular over the last couple of years and the number of alternatives available has risen. There are multiple service mesh open-source projects: Istio, Linkerd, Envoy and Conduit which can be deployed on any Kubernetes environment. The AWS App Mesh can be used with microservices running on Amazon Elastic Container Service (Amazon ECS), Amazon Elastic Container Service for Kubernetes (Amazon EKS), and Kubernetes running on Amazon EC2.

Read More
HashiCorp Consul supports Microsoft’s new Service Mesh Interface

HashiCorp Consul supports Microsoft’s new Service Mesh Interface

Today at KubeCon EU in Barcelona, Microsoft introduced a new specification, the Service Mesh Interface (SMI), for implementing service mesh providers into Kubernetes environments. The Service Mesh Interface (SMI) is a specification for service meshes that run on Kubernetes. It defines a common standard that can be implemented by a variety of providers.

Read More