Skip to content

feat: base for back pressure in talos ecosystem and usage in messenger#128

Draft
gk-kindred wants to merge 4 commits intomasterfrom
feature/messenger-back-pressure
Draft

feat: base for back pressure in talos ecosystem and usage in messenger#128
gk-kindred wants to merge 4 commits intomasterfrom
feature/messenger-back-pressure

Conversation

@gk-kindred
Copy link
Copy Markdown
Collaborator

  • Base struct TalosBackPressureConfig which could be added to any service in talos ecosystem with all the essential methods to capture and determine if back pressure is required.
  • Usage of TalosBackPressureConfig in Talos messenger service.

pub is_enabled: bool,
/// Max count before back pressue is enabled.
/// if `None`, back pressure logic will not apply.
pub max_threshold: Option<u32>,
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

If this is "max count" then its better if we named the attribute with workd "count" in it.

Please change the order.
is enabled
thencount and max count.

Comment on lines +11 to +12
/// Batch of items to process, when back pressure is enabled before disable logic is checked?
/// if None, no minimum check is done, and as soon as the count is below the max_threshold, back pressure is disabled.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Please have another look at the description. I am not able to follow the purpose of this parameter.

@gk-kindred gk-kindred marked this pull request as draft May 13, 2025 23:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants