One of Envoy’s many powers is traffic routing and load balancing. For any dynamic environment that’s subject to regular changes, it needs a dynamic configuration mechanism that is capable of enabling users to make those changes easily, and most importantly, with no downtime.
Tetrate’s Zack Butcher’s recent AMA with the United States Air Force Chief Software Officer, Nicolas Chaillan highlighted some significant achievements as a result of the Department of Defense’s move to Open source technology and DevSecOps. Platform One is a group of Air Force software developers that build and secure technology tools used across the DoD, as part of the Enterprise DevSecOps Initiative. Tetrate is a partner DoD is working with, on their journey to modernization.
Envoy Proxy has announced the release of 1.16 for general availability. The updates include the new support for ARM64 architecture, an update that has been a lot of work in the making with strong collaboration between ARM and the Envoy community.
New tooling is now available to make it easier for developers to create custom extensions for the Envoy proxy.
In this interview (also available as a Make it Mesh podcast), Tetrate Engineer Yaroslav Skopets, an Envoy contributor and GetEnvoy maintainer, explains how WebAssembly (Wasm) makes Envoy extensibility more accessible, and how developers can quickly get started with Tetrate’s open source GetEnvoy extensibility toolkit.
The release of Istio 1.7 was highly anticipated by the service mesh community and end-users because it addresses a problem that Tetrate was founded to solve: Bringing VMs into the mesh.
One of the most repeated pieces of advice for anyone getting started with microservices is to make sure you can see everything that’s going on inside your services. Leverage the power of observability. However, observability is a loaded term – so it’s valuable to understand what that terms mean, and what’s involved.
If you’re a beginner to the world of microservices, and you’re learning what the differences are between Virtual Machines (VMs) and Containers, it opens up a world of questions of what’s possible with bare metal, VMs and containers.
So many organizations find themselves straddling two worlds, the older ‘brownfield’ setup of Virtual Machines (VMs) and bare metal servers, and the ‘greenfield’ world of containers managed by Kubernetes. Managing a hybrid structure of these two types of infrastructures has a history of being time-consuming and complex, with an overburden on engineering to duplicate efforts.
The addition of a service mesh to any environment that straddles ‘old’ and ‘new’ allows you to abstract away from disparate infrastructures and refocus your organization to being an application-centric entity.
So you’ve heard about service mesh. You’ve been told this is the thing for your team and your organization. It’s got a laundry list of features and functionality that everyone in the market is saying you have to try if you’re going through some sort of digital transformation.
[Warning Klaxon] There’s more to it than that.