WePay Engineering: Keeping a service mesh monitored and highly available
A huge part of keeping any high volume SaaS business running smoothly is handling an enormous flow of data back and forth. It’s especially important for a company like WePay where we are handling people’s transactions and money. All our services have to be available 24/7 and running smoothly, swiftly and effectively. We’ve written previously about our engineering team’s efforts in this area, specifically how we use service mesh technologies to manage all the many services.
The WePay engineering blog covers many of the techniques and approaches we use and how we come to choose them. Mohsen Rezaei, Staff Software Engineer, just continued a series of posts there about our service mesh technologies with a piece on how we monitor and maintain availability of our service mesh. It’s a best practice piece that anyone interested in high availability services and service mesh technology will find valuable. The series of articles also covers how WePay manages its service mesh with Google Kubernetes Engine (GKE) and containerization patterns we’ve been experimenting with and using in GKE. If you are interested in these techniques or how one organization handles high volume transactions online, please take a look.