Pando - The Aspen Mesh Blog

Blog Posts With Category: 'general'

The Road Ahead for Service Mesh

Posted on Mar 29, 2018 by Zach Jory

This is the third in a blog series covering how we got to a service mesh, why we decided on the type of mesh we did and where we see the future of the space. If you’re struggling to manage microservices as architectures continue to become more complex, there’s a good chance you’ve at least heard of service mesh. For the purposes of this blog, I’ll assume you’re familiar with the basic tenets of a service mesh but check out the Istio page (the mesh we are building on top of) if you’re not yet up to speed.…

Service Mesh Architectures

Posted on Mar 23, 2018 by Andrew Jenkins

Note: This is the second in a series of posts, focused on the software architecture aspects of service mesh. To learn more about how we got here, check out The Path to Service Mesh. If you are building your software and teams around microservices, you’re looking for ways to iterate faster and scale flexibly. A service mesh can help you do that while maintaining (or enhancing) visibility and control. In this blog, I’ll talk about what’s actually in a Service Mesh and what considerations you might want to make when choosing and deploying one.…

The Path to Service Mesh

Posted on Mar 8, 2018 by

When we talk to people about service mesh, there are a few questions we’re always asked. These questions range from straightforward questions about the history of our project, to deep technical questions on why we made certain decisions for our product and architecture. To answer those questions we’ll bring you a three-part blog series on our Aspen Mesh journey and why we chose to build on top of Istio.…

Introducing Aspen Mesh - The Enterprise Service Mesh

Posted on Dec 6, 2017 by

Today we are very excited to introduce Aspen Mesh, an enterprise service mesh built on the open source project Istio. After talking to development and operations teams it became clear that microservices are great for development velocity, but the complexity and risk in these architectures lies in the service-to-service communication that microservices depend on. We have taken an application first approach to provide a communication fabric for microservices, called a service mesh.…