41Your architecture is queues and consumers. The golden signals assume request and response. Now what?▼hardNewUberNetflixStripe2 replies◆ premiumThere is no status code and no caller waiting, so latency and error rate stop meaning what they meant. The signals that replace them are age, lag and completion, and they answer a question the request-response set never had to ask.Open full answer →
35We doubled Kafka's partition count to fix growing lag, and lag grew instead. Walk me through what a rebalance does to a group.▼mediumNewUberLinkedInSnowflake◆ premiumMore partitions should mean more throughput, so why did the backlog deepen? Because rebalance behavior depends on the group protocol, and the way consumers divide work decides who pays for it.Open full answer →
34Retries make your event pipeline deliver duplicates. Which effects can you make exactly once, and where does that guarantee stop?▼hardNewUberDatabricksLinkedIn◆ premiumTrace a retry through the broker, database and external provider. The guarantee changes at each boundary, and a recorded intent does not prove a payment or email completed.Open full answer →
