What metrics would you use to evaluate Solace's Event Portal?

Introduction

Evaluating Solace's Event Portal requires a comprehensive approach to product success metrics. To address this challenge effectively, I'll follow a structured framework that covers core metrics, supporting indicators, and risk factors while considering all key stakeholders.

Step 1

Product Context

Solace's Event Portal is a design and management tool for event-driven architectures (EDA). It helps organizations visualize, model, and manage their event streams and applications. Key stakeholders include:

1. Enterprise Architects: Seeking to design and govern event-driven systems
2. Developers: Looking to understand and interact with event streams
3. Operations Teams: Monitoring and managing the EDA ecosystem
4. Business Analysts: Mapping business processes to event flows

User flow typically involves:

1. Designing event-driven architectures visually
2. Documenting event streams and schemas
3. Collaborating on designs with team members
4. Generating code artifacts for implementation
5. Monitoring and managing the deployed architecture

The Event Portal fits into Solace's broader strategy of enabling event-driven transformation for enterprises. It complements their PubSub+ event broker, offering a full-stack solution for EDA. Compared to competitors like Confluent's Schema Registry, Solace's Event Portal provides a more comprehensive, visual approach to EDA design and management.

In terms of product lifecycle, the Event Portal is in the growth stage, with increasing adoption but still evolving features and capabilities.