Bill Decoste

Field Engineer @soloio_inc

Bill DeCoste is a Solo.io Field Engineer working with enterprises to design and architect their application platform environments with Envoy Proxy, API Gateways, and Service Mesh. Prior to Solo.ioo, Bill held a variety of roles at Red Hat including Solutions Architect and Technical Account Manager for JBoss,  Principal Software Engineer for OpenShift and EJB3 and has also developed JEE courses and spent time as an independent consultant.

Presentation

Multi-Cluster Service Mesh Patterns, Configuration and Operations

Microservices promise greater agility and speed in delivering innovation to customers through digital experiences. As a set of many, small services that are loosely coupled together and often written in different languages and packages, microservices allow organizations to make changes to a portion of their application, quickly and without breaking the entire application - however this also creates new challenges.Service mesh solves the service-to-service communication challenge of microservices within a cluster and brings powerful capabilities like request routing, traffic observability, transport security, policy enforcement, and more. Architecting for highly available and resilient applications means the prevailing wisdom is to deploy microservices across many, small clusters to gain the benefits of fault tolerance, compliance or data access, disaster recovery, scalability, and more. 

Managing a service mesh deployment that is consistent and secure across multiple clusters is tedious, error prone at best, and raises questions like: 

  • How should I deploy and manage multiple clusters of service mesh?
  • What if my service meshes span across on-prem and cloud?
  • What traffic control or security policies do I need to consider across multiple clusters?

Service Mesh Hub is a Kubernetes-native control plane to unify and simplify the operation of multi-cluster service mesh including concerns like service discovery, identity and trust domains, access control, cross cluster traffic, failover and more. 

In this hands-on workshop, we will explore different service mesh deployment patterns, multi-cluster topologies, and how Service Mesh Hub can address the configuration and operations needs for these environments.

Each participant will have two dedicated Kubernetes clusters with Service Mesh Hub to:

  • Deploy Istio on each cluster
  • Discover and unify the clusters to form a virtual mesh
  • Configure cross cluster microservices communication
  • Create access control policies
  • Simulate traffic failover scenarios
DATE

Friday Nov 13 / 12:30PM PST (3 hours )

LEVEL

Intermediate

TOPICS Service MeshMicroservices ADD TO CALENDAR Add to calendar SHARE

3 weeks of live software engineering content designed around your schedule.

Don’t miss out! Save your seat now

Register
TOP