Clarify how to create scalable WebSocket setup [SPR-11450] #16076
our app sends around 300 million msgs a day.
Even though our heap size was well below 500mb and cpu usage was < 10%, we see that new relic shows an insane amount of time spent in the dispatcher servlet.
it seems the spring websocket architecture simply doesnt scale and if it does, there is again zero documentation on how to do that.
we can use an external messgaing queue, but it seems that will only impact the memory used for keeping the queue and not much else since the all the messages from the queue are passed back to the client through the app anyway.
It is also unclear if clustering the jvms with an external message queue would help. will the msgs sent back to client subscription be split into multiple jvms?
again no guidance/documentation on any of this. please clarify.
0 votes, 8 watchers
The text was updated successfully, but these errors were encountered:
I want to know if there is any solution for this or is there any better way to handle this (possibly reactive stack?), is there is any configuration setting that can release resources quickly? any recommendations for clientInbounChannel and clientOutboundChannel configurations?