servicemesh

Introducing Maesh: A Service Mesh for Kubernetes

On September 4th, 2019, Containous, a cloud infrastructure software provider, released Maesh, an open-source service mesh written in Golang and built on top of the reverse proxy and load balancer Traefik. Maesh promises to provide a lightweight service mesh solution that is easy to get started with and to roll out across a microservice application. Source: infoq.com

Announcing Maesh, a Lightweight and Simpler Service Mesh Made by the Traefik Team

We are proud to introduce Maesh, Containous’ new service mesh designed from the ground up to be straightforward, easy to install and easy to use. Maesh allows for visibility and management of the traffic that flows inside your Kubernetes cluster, which is just as important as the ingress and egress traffic. Built on top of Traefik, Maesh is a simple, yet full-featured service mesh. It is container-native and fits as your de-facto service mesh in your Kubernetes cluster.
Read more

The Service Mesh: It’s About Traffic

Oliver Gould talks about the Linkerd project, a service mesh hosted by the Cloud Native Computing Foundation, to give operators control over the traffic between their microservices. He shares the lessons they’ve learned helping dozens of organizations get to production with Linkerd and how they’ve applied these lessons to tackle complexity with Linkerd. Source: infoq.com

Minimize the blast radius of changes with Solo.io Gloo Gateway and Weaveworks Flagger

Progressive delivery is a term used to describe incremental rollout of changes to your system that optimizes for reducing risk and limiting “blast radius” of any negative outcomes of your changes. When we make a change to our system (code change or configuration change) we first expose this change to the smallest subset of users and analyze the impact of this change. If we find that the change has negligible or positive impact, we can continue to increase the subset of users that see this change.
Read more

Layer 7 Observability with Consul Service Mesh

Observability comes from the world of engineering and control theory. Control theory states that observability is itself a measure that describes “how well internal states of a system can be inferred from knowledge of external outputs”. In contrast to monitoring which is something you do, observability, is a property of a system. A system is observable if the external outputs, logging, metrics, tracing, health-checks, etc, allow you to understand its internal state.
Read more

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.
Read more

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. This allows for both standardization for end-users and innovation by service mesh providers. SMI enables flexibility and interoperability.
Read more

Hello Service Mesh Interface (SMI): A specification for service mesh interoperability

Service Mesh Interface (SMI) defines a set of common, portable APIs that provide developers with interoperability across different service mesh technologies, including Istio, Linkerd, and Consul Connect. Today we are excited to launch Service Mesh Interface (SMI) which defines a set of common, portable APIs that provide developers with interoperability across different service mesh technologies including Istio, Linkerd, and Consul Connect. SMI is an open project started in partnership with Microsoft, Linkerd, HashiCorp, Solo, Kinvolk, and Weaveworks; with support from Aspen Mesh, Canonical, Docker, Pivotal, Rancher, Red Hat, and VMware.
Read more

AWS App Mesh

AWS recently released a new service App Mesh during the 2019 summit which has generated a lot of interest from developers world-wide. This service is a great example of how Amazon is highly customer-focused in delivery of products/features to the market. Besides that, there is no additional charge for using the service!:-) With the advent of cloud, the importance of microservices has increased tremendously. In microservices architecture, large monolithic code-bases/architectures are broken down into smaller, more independent modules.
Read more

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