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

Designing Proper Usage #3

Open
azriel-healthpoint opened this issue May 27, 2024 · 0 comments
Open

Designing Proper Usage #3

azriel-healthpoint opened this issue May 27, 2024 · 0 comments

Comments

@azriel-healthpoint
Copy link

Heya, I'm designing a system in which we need to update Practitioner data periodically.

My understanding of NEMS is that events will be lightweight, and subscribers to a queue will look up the information related to that event. I think the linked information will be a delta/patch to the object that has changed, rather than a snapshot of the object.

My questions are:

  1. Is that understanding of what information is in each data item correct?

  2. Of the following designs for a guaranteed delivery queue, are they all "okay"?

    1. Always run the queue subscriber, so events are picked up and processed as they arrive.

      I'm assuming this is good, since it's the obvious intended usage pattern.

    2. Run a scheduled task every week, collect all the deltas, and apply them.

      This isn't how a delta queue normally should be processed, but is it alright?

      Note: I haven't familiarized myself with Solace yet, so let me know if "that's a bad idea ™️, best learn how Solace works" is the right thing to do.

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

No branches or pull requests

1 participant