buoyant.io

fuelcapital.com

Buoyant — Fuel Capital

http://www.fuelcapital.com/buoyant

Buoyant provides industrial-strength operability for cloud-native applications, allowing developers to identify issues before they escalate. The company released linkerd, an open source service mesh for cloud native applications that handles everything needed to make communication safe, reliable and performant - including load balancing, connection pooling, session management, instrumentation and routing. For more information, click here.

blog.buoyant.io

A Service Mesh for Kubernetes, Part I: Top-line service metrics

https://blog.buoyant.io/2016/10/04/a-service-mesh-for-kubernetes-part-i-top-line-service-metrics

A Service Mesh for Kubernetes, Part I: Top-line service metrics. What is a service mesh, and how is it used by cloud native apps—apps designed for the cloud? In this article, we’ll show you how to use linkerd. As a service mesh on Kubernetes, and how it can capture and report top-level service metrics such as success rates, request volumes, and latencies without requiring changes to application code. Pods are great, until they’re not. Encrypting all the things. Continuous deployment via traffic shifting.

blog.buoyant.io

A Service Mesh for Kubernetes, Part III: Encrypting all the things

https://blog.buoyant.io/2016/10/24/a-service-mesh-for-kubernetes-part-iii-encrypting-all-the-things

A Service Mesh for Kubernetes, Part III: Encrypting all the things. In this article, we’ll show you how to use linkerd as a service mesh to add TLS to all service-to-service HTTP calls, without modifying any application code. Note: this is one of a series of articles about linkerd, Kubernetes, and service meshes. Other installments in this series include:. Pods are great, until they’re not. Encrypting all the things. Continuous deployment via traffic shifting. Staging microservices without the tears.

blog.buoyant.io

linkerd on DC/OS for Service Discovery and Visibility

https://blog.buoyant.io/2016/10/10/linkerd-on-dcos-for-service-discovery-and-visibility

Linkerd on DC/OS for Service Discovery and Visibility. In our previous post, linkerd as a service mesh for Kubernetes. We showed you how to use linkerd on Kubernetes for drop-in service discovery and monitoring. In this post, we’ll show you how to get the same features on DC/OS. And discuss how this compares with DNS-based solutions like Mesos-DNS. Including at least one DNS-based option. But what exactly is service discovery, and how is it different from DNS? What is the IP address of that host? In fact...

blog.buoyant.io

Buoyant Blog

https://blog.buoyant.io/page/2

Industrial-strength operability for cloud-native applications. A Service Mesh for Kubernetes, Part V: Dogfood environments, ingress and edge routing. In this post we’ll show you how to use a service mesh of linkerd instances to handle ingress traffic on Kubernetes, distributing traffic across every instance in the mesh. We’ll also walk through an example that showcases linkerd’s advanced routing capabilities by creating a. Read more ». Read more ». Read more ». In our recent post about linkerd on Kuberne...

blog.buoyant.io

A Service Mesh for Kubernetes, Part IV: Continuous deployment via traffic shifting

https://blog.buoyant.io/2016/11/04/a-service-mesh-for-kubernetes-part-iv-continuous-deployment-via-traffic-shifting

A Service Mesh for Kubernetes, Part IV: Continuous deployment via traffic shifting. Beyond service discovery, top-line metrics, and TLS, linkerd also has a powerful routing language, called. That can be used to alter the ways that requests—even individual requests—flow through the application topology. In this article, we’ll show you how to use linkerd as a service mesh to do blue-green deployments of new code as the final step of a CI/CD pipeline. Note: this post was co-written with Kevin Lingerfelt.

blog.buoyant.io

A Service Mesh for Kubernetes, Part V: Dogfood environments, ingress and edge routing

https://blog.buoyant.io/2016/11/18/a-service-mesh-for-kubernetes-part-v-dogfood-environments-ingress-and-edge-routing

A Service Mesh for Kubernetes, Part V: Dogfood environments, ingress and edge routing. In this post we’ll show you how to use a service mesh of linkerd instances to handle ingress traffic on Kubernetes, distributing traffic across every instance in the mesh. We’ll also walk through an example that showcases linkerd’s advanced routing capabilities by creating a. Environment that routes certain requests to a newer version of the underlying application, e.g. for internal, pre-release testing. That Kubernete...

blog.buoyant.io

Slow Cooker: Load testing for tough software

https://blog.buoyant.io/2016/12/09/slow-cooker-load-testing-for-tough-software

Slow Cooker: Load testing for tough software. Linkerd, our service mesh for cloud-native applications, needs to handle very high volumes of production traffic over extended periods of time. In this post, we’ll describe the load testing strategies and tools we use to ensure linkerd can meet this goal. We’ll review some of the problems we faced when trying to use popular load testers. Finally, we’ll introduce slow cooker. As a service mesh, linkerd. For high-throughput network servers like linkerd, lifecyc...

dcos.io

Community | DC/OS

https://dcos.io/community

Join the DC/OS Community. Connect with our community of users and browse the latest DC/OS news. Are you interested in helping us make DC/OS even better? Check out our source code on GitHub. View repositories →. Our Slack channel is the best place to get help. Just send us a request to automatically receive your invitation. Join chat →. Want to stay in the loop and connect with other community members? Our public mailing list has all the latest updates. Join the discussion. Join users@dcos.io →.