Future of Service Mesh- Sidecar or Sidecarless or Proxyless? - Levine Kohavi, Mattix, Norman, Howard

As service mesh APIs become standards for operators and developers per the GAMMA initiative, there are still various different architecture choices to run service meshes, whether it is sidecar or sidecarless or even proxyless. What about proxies, Envoy C++ based proxy or Rust based proxy? What are the design considerations when choosing one architecture over another? This panel brings experts from Google, IBM, Solo and Microsoft to share their perspectives on sidecar, sidecarless and proxyless for future of service meshes and what you should consider when deciding which architecture is the right choice for your organization. Initial seeding questions: - We all understand sidecar architecture for service mesh, can you explain what sidecarless service mesh is? - Are people interested in a non-sidecar approach for service mesh? Why? - Does proxyless mean eBPF without proxy? - What about L7 processing - which architecture should we use?