1 Oct 2020
1:1 with Christian Posta
Service Meshes: Why are there so many of them?
What nuances and similarities do most have?
Why is Envoy underneath the hood of so many of them?
This appears to be the thing after Kubernetes, no?
Service Meshes: Why are there so many of them?
What nuances and similarities do most have?
Why is Envoy underneath the hood of so many of them?
This appears to be the thing after Kubernetes, no?
- 3 participants
- 55 minutes
8 Sep 2020
Don’t miss out! Join us at our upcoming events: EnvoyCon Virtual on October 15 and KubeCon + CloudNativeCon North America 2020 Virtual from November 17-20. Learn more at https://kubecon.io. The conferences feature presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects.
Multi Cluster and Multi Mesh Patterns - Christian Posta, Solo.io
The more services connected by a mesh, the more value in consistent observability, security, and routing can be achieved. In today's complex heterogeneous environments, deploying everything into a single cluster and single mesh can be impossible. In this talk we look at some of the options and challenges for adopting a service mesh across multiple clusters and potentially across multiple meshes. We look at the challenges such as federating identity, single pane of glass for observability, developing policies et. al, as well as ways to solve these challenges. The patterns discussed here are not mesh specific and will use Istio, Linkerd, and App Mesh as examples.
https://sched.co/abc9
Multi Cluster and Multi Mesh Patterns - Christian Posta, Solo.io
The more services connected by a mesh, the more value in consistent observability, security, and routing can be achieved. In today's complex heterogeneous environments, deploying everything into a single cluster and single mesh can be impossible. In this talk we look at some of the options and challenges for adopting a service mesh across multiple clusters and potentially across multiple meshes. We look at the challenges such as federating identity, single pane of glass for observability, developing policies et. al, as well as ways to solve these challenges. The patterns discussed here are not mesh specific and will use Istio, Linkerd, and App Mesh as examples.
https://sched.co/abc9
- 1 participant
- 32 minutes
8 Sep 2020
Don’t miss out! Join us at our upcoming events: EnvoyCon Virtual on October 15 and KubeCon + CloudNativeCon North America 2020 Virtual from November 17-20. Learn more at https://kubecon.io. The conferences feature presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects.
Welcome & Opening Remarks - Christian Posta, solo.io
https://sched.co/ZWiY
Welcome & Opening Remarks - Christian Posta, solo.io
https://sched.co/ZWiY
- 1 participant
- 11 minutes
4 Sep 2020
Don’t miss out! Join us at our upcoming events: EnvoyCon Virtual on October 15 and KubeCon + CloudNativeCon North America 2020 Virtual from November 17-20. Learn more at https://kubecon.io. The conferences feature presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects.
Panel: Ask Me Anything About Service Mesh - Lin Sun & Daniel Berg IBM; Christian Posta, Solo.io; Oliver Gould, Buoyant; & Sven Mawson, Google
As part of the cloud native journey, users are leveraging service mesh to solve the rising challenges of microservices in a consistent manner such as how to observe microservices, how to handle network failures, how to control traffic and how to secure microservices etc. without redeploying their services. Join us for a live interactive session where our panel of service mesh experts will address your most challenging inquiries around service mesh!
https://sched.co/ZejT
Panel: Ask Me Anything About Service Mesh - Lin Sun & Daniel Berg IBM; Christian Posta, Solo.io; Oliver Gould, Buoyant; & Sven Mawson, Google
As part of the cloud native journey, users are leveraging service mesh to solve the rising challenges of microservices in a consistent manner such as how to observe microservices, how to handle network failures, how to control traffic and how to secure microservices etc. without redeploying their services. Join us for a live interactive session where our panel of service mesh experts will address your most challenging inquiries around service mesh!
https://sched.co/ZejT
- 5 participants
- 36 minutes
25 Aug 2020
Christian Posta (Solo.io) and Dan Berg (IBM and Istio Project) are going live in this next Hoot episode to talk about the latest Istio 1.7 release.
- 2 participants
- 48 minutes
17 Mar 2020
Hoot is a livestream by engineers talking about and trying out new technology.
Get to Know Service Mesh
We kick this off with a series on service mesh - each episode will look into a different service mesh provider.
* Istio
* Linkerd
* Consul
* AWS App Mesh
* More meshes like Kuma and Maesh
* Compare and contrast the different service meshes, explain their unique features and how to choose which one(s) to use for your applications.
Get to Know Service Mesh
We kick this off with a series on service mesh - each episode will look into a different service mesh provider.
* Istio
* Linkerd
* Consul
* AWS App Mesh
* More meshes like Kuma and Maesh
* Compare and contrast the different service meshes, explain their unique features and how to choose which one(s) to use for your applications.
- 1 participant
- 41 minutes
7 Jan 2020
Hoot is a livestream by engineers talking about and trying out new technology.
Get to Know Service Mesh
We kick this off with a series on service mesh - each episode will look into a different service mesh provider.
* Istio
* Linkerd
* Consul
* Community requests -- suggest a service mesh
* Compare and contrast the different service meshes, explain their unique features and how to choose which one(s) to use for your applications.
Get to Know Service Mesh
We kick this off with a series on service mesh - each episode will look into a different service mesh provider.
* Istio
* Linkerd
* Consul
* Community requests -- suggest a service mesh
* Compare and contrast the different service meshes, explain their unique features and how to choose which one(s) to use for your applications.
- 1 participant
- 44 minutes
17 Dec 2019
Join us for Kubernetes Forums Seoul, Sydney, Bengaluru and Delhi - learn more at kubecon.io
Don't miss KubeCon + CloudNativeCon 2020 events in Amsterdam March 30 - April 2, Shanghai July 28-30 and Boston November 17-20! Learn more at kubecon.io. The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects
The Truth About the Service Mesh Data Plane - Christian Posta, Solo.io
The exploration of service mesh for any organization comes with some serious questions. What data plane should I use? How does this tie in with my existing API infrastructure? What kind of overhead do sidecar proxies demand? As I've seen in my work with various organizations over the years "if you have a successful microservices deployment, then you have a service mesh whether it’s explicitly optimized as one or not."
In this talk, we seek to understand the role of the data plane and how to pick the right component for the problem context. We start off by establishing the spectrum of data-plane components from shared gateways to in-code libraries with service proxies being along that spectrum. We clearly identify which scenarios would benefit from which part of the data-plane spectrum and show how modern service meshes including Istio, Linkerd, and Consul enable these optimizations.
Don't miss KubeCon + CloudNativeCon 2020 events in Amsterdam March 30 - April 2, Shanghai July 28-30 and Boston November 17-20! Learn more at kubecon.io. The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects
The Truth About the Service Mesh Data Plane - Christian Posta, Solo.io
The exploration of service mesh for any organization comes with some serious questions. What data plane should I use? How does this tie in with my existing API infrastructure? What kind of overhead do sidecar proxies demand? As I've seen in my work with various organizations over the years "if you have a successful microservices deployment, then you have a service mesh whether it’s explicitly optimized as one or not."
In this talk, we seek to understand the role of the data plane and how to pick the right component for the problem context. We start off by establishing the spectrum of data-plane components from shared gateways to in-code libraries with service proxies being along that spectrum. We clearly identify which scenarios would benefit from which part of the data-plane spectrum and show how modern service meshes including Istio, Linkerd, and Consul enable these optimizations.
- 1 participant
- 31 minutes
22 Nov 2019
Join us for Kubernetes Forums Seoul, Sydney, Bengaluru and Delhi - learn more at kubecon.io
Don't miss KubeCon + CloudNativeCon 2020 events in Amsterdam March 30 - April 2, Shanghai July 28-30 and Boston November 17-20! Learn more at kubecon.io. The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects
Tutorial: Service Mesh for the Developer Workflow - Christian Posta, Solo.io & Nic Jackson, Hashicorp (Limited Available Seating; First-Come, First-Served Basis)
Please bring your laptop fully charged as we will have limited charging stations available in the room. Service mesh is often presented as a solution for network engineering and system operability, increasing security, reliability, and observability. However, service mesh is also an incredibly useful tool for developers, and understanding how to leverage this technology can dramatically simplify your day to day workflow. By leveraging free and open-source tools and a scenario-based approach, we will illustrate how a service mesh can help with application resilience, observability, and debugging. By the end of this workshop you will understand: How to use metrics and distributed tracing effectively Reliability patterns like retries, timeouts, and circuit breaking How to leverage Canary deployments How you can effectively debug distributed systems The cloud-native, open-source technology used in this tutorial include: Envoy Prometheus Gloo shot Consul Service Mesh Loop Squash Open Census
https://sched.co/Uaeb
Don't miss KubeCon + CloudNativeCon 2020 events in Amsterdam March 30 - April 2, Shanghai July 28-30 and Boston November 17-20! Learn more at kubecon.io. The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects
Tutorial: Service Mesh for the Developer Workflow - Christian Posta, Solo.io & Nic Jackson, Hashicorp (Limited Available Seating; First-Come, First-Served Basis)
Please bring your laptop fully charged as we will have limited charging stations available in the room. Service mesh is often presented as a solution for network engineering and system operability, increasing security, reliability, and observability. However, service mesh is also an incredibly useful tool for developers, and understanding how to leverage this technology can dramatically simplify your day to day workflow. By leveraging free and open-source tools and a scenario-based approach, we will illustrate how a service mesh can help with application resilience, observability, and debugging. By the end of this workshop you will understand: How to use metrics and distributed tracing effectively Reliability patterns like retries, timeouts, and circuit breaking How to leverage Canary deployments How you can effectively debug distributed systems The cloud-native, open-source technology used in this tutorial include: Envoy Prometheus Gloo shot Consul Service Mesh Loop Squash Open Census
https://sched.co/Uaeb
- 4 participants
- 1:31 hours
31 Jul 2019
An application gateway is a piece of infrastructure that helps existing applications incrementally adopt new architectures like microservices and serverless. It is not as single purposed as an API gateway, and not as complicated as a full service mesh and provides immediate value. In this talk we’ll explore this emerging pattern. In this talk, we'll explore how to leverage an application gateway to get value out of your existing architecture while moving to microservices and serverless. This application gateway uses technologies like Envoy Proxy, GraphQL, and HTTP/2 to help solve some of these problems
http://www.jbcnconf.com/2019/infoTalk.html?id=5c3e5dbb38da16698cf41b28
http://www.jbcnconf.com/2019/infoTalk.html?id=5c3e5dbb38da16698cf41b28
- 2 participants
- 52 minutes
17 May 2019
Service mesh abstracts the network from developers to solve three main pain points:
How do services communicate securely with one another
How can services implement network resilience
When things go wrong, can we identify what and why
Service mesh implementations usually follow a similar architecture: traffic flows through control points between services (usually service proxies deployed as sidecar processes) while an out-of-band set of nodes is responsible for defining the behavior and management of the control points. This loosely breaks out into an architecture of a "data plane" through which requests flow and a "control plane" for managing a service mesh.
Different service mesh implementations use different data planes depending on their use cases and familiarity with particular technology. The control plane implementations vary between service-mesh implementations as well. In this talk, we'll take a look at three different control plane implementations with Istio, Linkerd and Consul, their strengths, and their specific tradeoffs to see how they chose to solve each of the three pain points from above. We can use this information to make choices about a service mesh or to inform our journey if we choose to build a control plane ourselves. - Captured Live on Ustream at http://www.ustream.tv/channel/craftconf3
How do services communicate securely with one another
How can services implement network resilience
When things go wrong, can we identify what and why
Service mesh implementations usually follow a similar architecture: traffic flows through control points between services (usually service proxies deployed as sidecar processes) while an out-of-band set of nodes is responsible for defining the behavior and management of the control points. This loosely breaks out into an architecture of a "data plane" through which requests flow and a "control plane" for managing a service mesh.
Different service mesh implementations use different data planes depending on their use cases and familiarity with particular technology. The control plane implementations vary between service-mesh implementations as well. In this talk, we'll take a look at three different control plane implementations with Istio, Linkerd and Consul, their strengths, and their specific tradeoffs to see how they chose to solve each of the three pain points from above. We can use this information to make choices about a service mesh or to inform our journey if we choose to build a control plane ourselves. - Captured Live on Ustream at http://www.ustream.tv/channel/craftconf3
- 2 participants
- 47 minutes