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

Specify a rendezvous service for consumer reconciliation #271

Open
amrc-benmorrow opened this issue May 3, 2024 · 0 comments
Open

Specify a rendezvous service for consumer reconciliation #271

amrc-benmorrow opened this issue May 3, 2024 · 0 comments

Comments

@amrc-benmorrow
Copy link
Contributor

This needs to be able to track requests made by consumers and fulfillments coming from the reconciliation service. This means it needs stable storage (this is another database). We also need Sparkplug notification; at minimum change-notify, though it would be good to have enough information available that at least some activities didn't need to hit the REST API.

It's possible this function could be filled by the ConfigDB, but getting the permissions right is currently impossible. It's also difficult to see how to handle multiple sessions for the same user. If we keep all of a user's requests under their own UUID we then need to handle concurrent updates; we have If-Match, but this still relies heavily on each application being careful to only modify its own state. If we mint a new UUID for each application session this again become difficult to grant permissions for and ends up with an awful lot of UUIDs registered.

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