AWS App Mesh vs. Greymatter

If your workloads are primarily based on AWS infrastrucure, where you might have EC2, EKS, Cloud Watch solutions, this service is native and good for you to maintain application level metworking. Also if you want to assess how secure inter service traffic could be achieved without a lot of custom writing, AWS App Mesh is a fine solution.

Incentivized

• Standardization of microservices communication.
• Traceability and visibility of communication across microservices.
• Identify and Isolate issues in microservices communication.
• Monitoring and sending data to CloudWatch.

Incentivized

• Complex setup and configuration - should provide a simplified onboarding process.
• There is no RBAC style policies, which could improve security and control
• No native rate limiting and circuit breaking.

Incentivized

We rated AWS App Mesh as part of a comparison with Microsoft Azure AKS + Istio. While we rated its usability 6/10, recognizing its strengths in AWS-native integration, the difficult learning curve and limited flexibility made it less appealing for broader use. Also AWS announced the retirement of AWS App Mesh by the end of this year.

Incentivized

Istio is high on operational costs as compared to AppMesh. HIgher learning curve for Istio as compared to AppMesh. Multi cluster support in AWS. App Mesh has IAM integration which is a plus for AWS workloads.

Incentivized

• High ROI as it facilitates operational monitoring and root cause analysis.
• Ensures to re-route and distribute traffic sustaining operational availability and performance - +ve for ROI.
• Service discovery enables service run time governance - +ve for ROI.

Incentivized