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

How to save CoAP server observable state in central memory for multiple server instances #77

Open
iumarabbas opened this issue Jun 11, 2024 · 0 comments

Comments

@iumarabbas
Copy link

I have an infrastructure where CoAP server (CoAP.NET library) receives message from client 1 and publish this message to subscribers of this topic (let suppose subscriber 1).

When client 2 sends message then it is notified to subscriber 2.

We need to scale out CoAP server to deploy it in mulitple instances and in that case each CoAP server will keep subscribers list (observers state) in memory) so the state is not in central location.

We want to save this observer state in some central memory or cache where all instances of CoAP server will use the same subscription state and notify clients accordingly.

Please suggest of we can integrate Redis or some other queue with CoAP.

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