Student pricing is available for eligible university email holders. View plans

NextSprints
NextSprints Icon NextSprints Logo
Product Design

Master the art of designing products

Product Improvement

Identify scope for excellence

Product Success Metrics

Learn how to define success of product

Product Root Cause Analysis

Ace root cause problem solving

Product Trade-Off

Navigate trade-offs decisions like a pro

All Questions

Explore all questions

Meta (Facebook) PM Interview Course

Practice Meta-focused PM cases

Amazon PM Interview Course

Practice Amazon-focused PM cases

Apple PM Interview Course

Practice Apple-focused PM cases

Google PM Interview Course

Practice Google-focused PM cases

Microsoft PM Interview Course

Practice Microsoft-focused PM cases

All Courses

Explore all courses

1:1 PM Coaching

Practice in a one-to-one session

Resume Review

Narrate impactful stories via resume

Guides Pricing
nextsprints logo

Not a member?

By proceeding, you agree to our Terms of Use and confirm you have read our Privacy and Cookie Statement.

nextsprints logo

Register to continue.

Login with Google Login with LinkedIn

By proceeding, you agree to our Terms of Use and confirm you have read our Privacy and Cookie Statement .

Company focus

Solace

Why has Solace's PubSub+ Event Broker seen a 20% drop in message throughput over the past month?

Prepared by NextSprints

15 mins
Report an error
Technical Analysis Problem-Solving Data Interpretation Enterprise Software Cloud Computing Financial Services Performance Optimization Root Cause Analysis Messaging Systems Event-Driven Architecture
Product Management Root Cause Analysis Question: Investigating Solace PubSub+ Event Broker performance decline

Introduction

Solace's PubSub+ Event Broker, a critical component in event-driven architectures, has experienced a concerning 20% drop in message throughput over the past month. This decline in performance could significantly impact the reliability and efficiency of systems relying on this event broker. To address this issue, I'll employ a systematic approach to identify, validate, and resolve the root cause while considering both immediate and long-term implications.

Framework overview

This analysis follows a structured approach covering issue identification, hypothesis generation, validation, and solution development.

Step 1

Clarifying Questions (3 minutes)

  • Looking at the timing, I'm thinking there might be a correlation with recent system changes. Have there been any updates or modifications to the PubSub+ Event Broker or related systems in the past 1-2 months?

Why it matters: Recent changes could directly impact performance. Expected answer: Yes, there was a minor update to the broker's configuration. Impact on approach: If confirmed, we'd focus on the update's impact and potential rollback.

  • Considering the scale of the throughput drop, I'm wondering about the load patterns. Has there been any significant change in the volume or pattern of messages being processed?

Why it matters: Unusual load patterns could explain the performance dip. Expected answer: No significant changes in overall volume, but some shifts in peak times. Impact on approach: We'd investigate how these shifts might be affecting the broker's performance.

  • Given the nature of event brokers, I'm curious about the types of messages being processed. Has there been any change in the message complexity or size in the affected period?

Why it matters: Changes in message characteristics could impact processing efficiency. Expected answer: Some increase in message size for certain types of events. Impact on approach: We'd analyze how these larger messages are affecting the system's performance.

  • Thinking about the broader ecosystem, I'm wondering about client applications. Have there been any changes or issues reported with the applications consuming messages from the broker?

Why it matters: Client-side issues could be contributing to or masking the real problem. Expected answer: No major changes reported, but some clients have noted slower processing. Impact on approach: We'd investigate both broker and client-side performance metrics.

Subscribe to access the full answer

Image of author NextSprints

NextSprints

Updated Jan 22, 2025