NGINX's gRPC module has an issue that requires a long keepalive to be set to ensure long streams stay open. Reconnects may be a good short-term solution, but ultimately during the time the client remains disconnected, events may be missed which means that the state of the application would need to be entirely invalidated. With WebSockets as the streaming method, there are no disconnects and do not require you to specify a keepalive timeout. In addition, gRPC has other load balancing complexities that can cause problems (mainly that connections are sticky and reused for as long as possible).
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
NGINX's gRPC module has an issue that requires a long
keepaliveto be set to ensure long streams stay open. Reconnects may be a good short-term solution, but ultimately during the time the client remains disconnected, events may be missed which means that the state of the application would need to be entirely invalidated. With WebSockets as the streaming method, there are no disconnects and do not require you to specify a keepalive timeout. In addition, gRPC has other load balancing complexities that can cause problems (mainly that connections are sticky and reused for as long as possible).