Skip to content

[DX-885] Addresses conflation discoverability docs gap#3231

Merged
umair-ably merged 2 commits intomainfrom
DX-885-conflation
Mar 3, 2026
Merged

[DX-885] Addresses conflation discoverability docs gap#3231
umair-ably merged 2 commits intomainfrom
DX-885-conflation

Conversation

@umair-ably
Copy link
Contributor

Description

Addresses conflation discoverability docs gap as per the llm-eval docs audit

Checklist

@coderabbitai
Copy link

coderabbitai bot commented Mar 2, 2026

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch DX-885-conflation

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@umair-ably umair-ably changed the title Addresses conflation discoverability docs gap [DX-885] Addresses conflation discoverability docs gap Mar 2, 2026
@umair-ably umair-ably marked this pull request as ready for review March 2, 2026 13:33
@umair-ably umair-ably requested review from AndyTWF and GregHolmes March 2, 2026 13:33

Consider enabling conflation when:
- A channel receives frequent updates (even as low as 2-3 messages per second with the same conflation key) and consumers only need the latest value.
- Your use case involves streaming prices, sensor readings, location coordinates, or other continuously-updating values.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

All of these are dependent on the point above - either every value is important, or it isn't. It doesn't matter if you're streaming prices, if every message is important you wouldn't use conflation.

Do we need to word this as example use-cases?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fair, removed this bullet point altogether. The others make the case we want to make

- You want to reduce message delivery volume and associated costs.

<Aside data-type='important'>
Conflation discards intermediate messages. Within each conflation interval, only the last message for each conflation key is delivered to subscribers. All earlier messages within that window are permanently dropped. They are not stored, not available via history, and cannot be recovered. Do not use conflation for data where every message matters, such as chat messages, transaction events, or ordered commands.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Signpost to batching?

@umair-ably umair-ably requested a review from AndyTWF March 3, 2026 10:56
@umair-ably umair-ably enabled auto-merge (squash) March 3, 2026 20:59
@umair-ably umair-ably merged commit 953b8e6 into main Mar 3, 2026
7 checks passed
@umair-ably umair-ably deleted the DX-885-conflation branch March 3, 2026 21:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants