Skip to content

performance: Support asynchronous sending of result messages #29

Closed

Description

At the moment when using the consumer, process, produce loop - the produced messages are sent to the brokers synchronously. This is simpler, but sending asynchronously might be faster. If we want to commit offsets correctly though, we have to hold onto the work unit in a limbo state, until the async produce result has completed.

This would be easily added as another step in the state machine for a unit of work. However it may be tricky to handle producer send time outs, if too many messages are waiting to be sent with the producer, and the producer starts timing them out. In this case they could be retried easily, but back pressure must be put into the system to prevent further messages from being queued up which would exacerbate the problem.

Activity

  1. changed the title [-]Support asynchronous sending of result messages (performance)[/-] [+]performance : Support asynchronous sending of result messages[/+] on Dec 14, 2020
  2. changed the title [-]performance : Support asynchronous sending of result messages[/-] [+]performance: Support asynchronous sending of result messages[/+] on Dec 14, 2020
  3. johnbyrnejb commented on Jul 7, 2023

    @johnbyrnejb
    Contributor

    Closing Issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions