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

Trigger notifications after storage #186

Open
2 tasks
mathiaszinnen opened this issue Sep 8, 2020 · 0 comments
Open
2 tasks

Trigger notifications after storage #186

mathiaszinnen opened this issue Sep 8, 2020 · 0 comments
Labels
AMSE Small tasks for AMSE students

Comments

@mathiaszinnen
Copy link
Contributor

Currently, notifications are triggered after successful data transformations. This can lead to race conditions if a client waits for notification and instantly pulls the data. Instead, notifications should be triggered after successful data storage.
This entails two tasks:

  • The storage-mq service needs to publish events to storagemq after data persistence.
  • The notification service needs to listen for these events instead of transformation events (change the rabbitmq subscription)
@mathiaszinnen mathiaszinnen added the AMSE Small tasks for AMSE students label Sep 8, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
AMSE Small tasks for AMSE students
Projects
None yet
Development

No branches or pull requests

1 participant