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

Clustering - Horizontal Scaling, Production deployment more than one node #216

Open
ysaakpr opened this issue Aug 4, 2023 · 2 comments
Open

Comments

@ysaakpr
Copy link

ysaakpr commented Aug 4, 2023

I got a start with this library, and it works fantastic for the internal setup. But what about production grade deployment.

I see no sample of scaling or clustered deployment of the same. going through the library i find that its might not yet support the multi node behaviour since the queue and connection registrys are in memory.

Any notes/thoughts on how to make it multi node ?

@ysaakpr
Copy link
Author

ysaakpr commented Aug 6, 2023

#59 found this ticket as well. But no progress or updates.

@xBlaz3kx
Copy link
Contributor

xBlaz3kx commented Oct 18, 2023

Hey,

we'll use this in production soon. As stated in the issue mentioned above, we created a separate service for handling OCPP connections and we utilize message brokers to issue requests to the charge points through this service.

I don't think you'll be able to make this multi node, because of the nature of websockets, as they persist a connection to a single node (without a load balancer).

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

2 participants