You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 ?
The text was updated successfully, but these errors were encountered:
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).
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 ?
The text was updated successfully, but these errors were encountered: