One of the popular solutions nowadays in building web-based real-time communication is WebSocket, which utilizes a TCP connection in establishing client-server communication. This communication strategy allows saving client sessions at the server side, which enhances bi-directional communication between the client and the server. Lots of payload converters and serializers are available nowadays that can help scrutinize and persist messages for security and audit purposes. Moreover, communication using WebSocket is lighter than the usual HTTP-based strategy, since the header information involved during the process is less. In the WebSocket client and in server exchange, the transfer of data per frame is at least 2 bytes compared to HTTP-based communications, which can take at least 8 Kb per frame. Some requirements may not apply low-latency communication, which will always need an HTTP header exchange.