Remesh delivers Continuous Release for Kubernetes and Microservices based applications.
To learn more about Continuous Release see our blog post: Introducing Continuous Release.

Building on the Cloud Native stack

In order to implement Continuous Release concepts, including capabilities like canray releases, testing in production and applied observability, we decided to start from, and build on, the Cloud Native stack that we know so well and love.

Our point of view of the world start with Kubernetes. This allows us to run anywhere, cloud or on-premises. It also provides a common Infrastructure as Code mechanism for us to build on by leveraging Kuberntes CRDs and Controllers. To take this a step further, it open the gate for GitOps based operations that we find naturally compatible with our solution.

We recognized some capable open source tools as good building blocks to work with, such as Envoy (embeddable proxy), Prometheus (metrics collection) and Jaeger (Distributed tracing). But instead of using them directly, we chose to base on the promising Istio Service Mesh, which wraps those tools into a convenient platform.

By building on top of Kubernetes and Istio, we ensure that the solution is backed by a robust platform that is supported by the industry. In fact, chances are your company already chose Kubernetes and Istio anyway, so Remesh will fit right in.

Abstracting the Service Mesh

When we designed Remesh we wanted to make it as user centric as possible, so we thought about how people would want to model the release of their software instead of how current tools like Istio can be used to solve this problem. The result was a simpler model that allows you to describe the layout of your microservices and the way you want to release them. We then bridged the gap between the Remesh model, and Istio implementation details by creating a Kubernetes Operator that re-programs the Istio service mesh to match your desired configuration. This is the core of the Remesh open source project.

Supporting coexisting releases

The Remesh model brings a powerful new way to describe complex microservices environments where multiple versions of your services coexist in production. You do this by expressing the layout of the release, which lists of the relevant services and their versions. Remesh will take care of merging the layouts into a functional Service Mesh.

Segmentation and Targeting

Once you organize your microservices into releases, you can manage the exposure of those releases to users. Remesh allows you to slice your user audience into segments based on common criteria such as HTTP headers and use those segments as the target of releases. The act of releasing works on the layout level, instead of individual services. This is a vast improvement over the mixing and matching of compatible service versions manually.

Open Source

Bevyx is an Open Source company. We love open source and we appreciate the years of investment, by individuals and companies, that helped build the thriving ecosystem that we have today.
Our aim is to make open source products, and we encourage anyone to collaborate with us. Moreover, we are investing in the open source stack that we build on by actively participating and contributing back to the open source technologies that we use.