How would you measure the success of Solo.io's Gloo Edge API gateway?

Introduction

Measuring the success of Solo.io's Gloo Edge API gateway requires a comprehensive approach that considers multiple stakeholders and metrics. To effectively evaluate this product success metrics problem, I'll follow a structured framework covering core metrics, supporting indicators, and risk factors while considering all key stakeholders.

Step 1

Product Context

Gloo Edge is an API gateway and Kubernetes Ingress controller designed to provide advanced traffic management, security, and observability features for microservices and cloud-native applications. Key stakeholders include:

1. DevOps teams: Seeking efficient management of API traffic and service mesh integration
2. Developers: Looking for easy configuration and extensibility
3. Security teams: Concerned with API security and access control
4. Business leaders: Interested in cost-effectiveness and scalability

User flow typically involves:

1. Installation and deployment of Gloo Edge in a Kubernetes cluster
2. Configuration of routes, security policies, and integrations
3. Ongoing management and monitoring of API traffic

Gloo Edge fits into Solo.io's broader strategy of providing a comprehensive suite of tools for modern, cloud-native application networking. It competes with other API gateways like Kong and Ambassador, differentiating itself through its Envoy-based architecture and tight Kubernetes integration.

In terms of product lifecycle, Gloo Edge is in the growth stage, with an established user base but still evolving features and expanding market share.