Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Discovery] Ensure event bus events can't be lost when producing #178

Open
6 tasks
robrap opened this issue Jun 13, 2023 · 1 comment
Open
6 tasks

[Discovery] Ensure event bus events can't be lost when producing #178

robrap opened this issue Jun 13, 2023 · 1 comment
Labels
event-bus Work related to the Event Bus.

Comments

@robrap
Copy link
Contributor

robrap commented Jun 13, 2023

We may end up with multiple types of solutions that are applicable in different solutions, but we should know more about how to ensure events can't be lost when producing.

Questions:

  • What are the various ways that Confluent recommends?
  • Is the Outbox pattern a viable solution, and what would it take to implement, including parallel-processing of the outbox itself.
  • Is producing using sync instead of async acceptable in any situations as a potentially easy way?
  • Do different ack configs help with this, or does this just handle a certain class of problems?
  • What does happen now when a server is stopped? Does the batch make it to Confluent?
@robrap
Copy link
Contributor Author

robrap commented Sep 13, 2023

This ticket may have been displaced by openedx/openedx-events#251. Once movement is made on that, it may make sense to close out this ticket.

@jristau1984 jristau1984 moved this to Backlog in Arch-BOM Jul 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
event-bus Work related to the Event Bus.
Projects
None yet
Development

No branches or pull requests

1 participant