How mailgun adopted service mesh with vulcand and NGINX

Click for: original source

Derrick J Wippler description how and why they jumped on service mesh bandwagon. He will tell you what is a service mesh, why they have adopted it at Mailgun, and how are they using it to deliver their software. Service mesh has officially become a thing, thanks to the launch of Istio (a joint collaboration between IBM, Google, and Lyft) and the adoption of linkerd by big companies like PayPal and Ticketmaster.

In simple terms, a service mesh is a bit of software (usually a proxy) that handles service-to-service communication in a fast and resilient manner.

You will also find:

  • How they created vulcand as reverse proxy first and then extended it
  • How Mailgun manages service mesh routes
  • Exposing service mesh as a public api

The major advantage to service mesh is that it allows for high resiliency (no load balancer single point of failure), built-in service discovery, and zero downtime releases. Charts with architecture are provided as well. Good read!

[Read More]

Tags microservices kubernetes software-architecture