Okay, thanks for the information.
The problem with doing the pubsub in NodeJS entirely is the way NodeJS handle connections. Each is separated and is accompanied by a big overhead from NodeJS. What would be great is a way to interact with the pubsub server not by config but with an API. This would allows, for example, the execution of middlewares when a user publishes a message (to filter them or something else). 
Right now, I&#x27;m using two websockets, one to Nginx PushStream only to receive messages and another to the NodeJS server to publish messages. The NodeJS server is used to parse the messages, format them, authenticate the user and apply the middlewares before publishing the message to Redis. Then, each NodeJS get the message from Redis and POST it to Nginx.
The problem here is that there is two sockets for each user and the complexity involved with the communication between Nginx and NodeJS. That&#x27;s why a really performant standalone websocket engine with an extensive API would be awesome.