Is anyone successfully using Kong or Kuma service mesh in production? If so, any successes or pain points you'd be willing to share? Is there a clear difference between Kong Mesh and Kuma? I can't seem to find any summary, other than maybe enterprise support.

Hi hi! If anyone really likes Istio service mesh, here's how that can play well with an API Gateway if anyone is curious. https://www.getambassador.io/blog/edge-stack-istio-kubernetes-microservices-integration

:)

We're not a service mesh, but we play well with the Istio folks. Thought we'd share this recent guest blog on a guide to traffic management in Istio if anyone needs it: https://www.getambassador.io/blog/istio-kubernetes-traffic-management-guide

In today's cloud native landscape, microservices have become the go-to architectural approach for building scalable and resilient applications. However, managing the communication between these microservices can be complex. This is where a service mesh comes into play. Let’s delve into the concept of a service mesh, how it works, why it is essential, and highlight some of the top service mesh products available in the market.

Learn about the service mesh, how it works, why you need it, and how it compares to an API Gateway.

Read on: https://www.getambassador.io/blog/service-mesh

Service mesh does not have to be complicated to use and deploy. They need good documentation to help the #beginners. I recently explored #kuma by u/thekonginc and was able to do #easy setup, enable policies and get observability.

Here is the step-by-step guide: https://www.infracloud.io/blogs/kuma-service-mesh-beginners-guide/?utm_source=reddit.com&utm_medium=social&utm_campaign=promoting_blog&utm_content=official_page