Hacker News Reader

As you do more and more research of the options, you will find that each "service mesh solution" has its own distinct set of pros and cons.

What was the driving factor in choosing a service mesh?

View on HN

We aren't 100% sold on service mesh yet, but it seems appropriate for our needs as we are going multi-region soon and we already have a micro-service style architecture. At some point an abstraction layer is needed to handle routing amongst services and provide failover to a different region if one goes out for example.

I know there are other ways to do this, but they all seemed clunky in comparison. Care to share any pros/cons of mesh solutions you've used?

I'd also add that the current service mesh solutions are all pretty immature. Linkerd is the most mature, but Buoyant is splitting resources and doing Conduit. There's Cilium. There's Tigera/Calico (sort of). There's now Consul Connect. And of course Istio.

Reply on news.ycombinator.com