WAMP is interesting to scale WebSocket (WS) application, going from 1 websocket procesus to several. You can do the same with Redis or else. Otherwise said it

WAMP is interesting to scale WebSocket (WS) application, going from 1 websocket procesus to several. You can do the same with Redis or else. Otherwise said it allows to create clustered websocket (WS) applications. E.g. two clients are connected to the same web chat room but via different WS servers, WAMP will allow to forward messages happening in one websocket server/processus to the other, otherwise their would be the equivalent of an IRC net split. You can do that with Redis too, but with WAMP “it just works”(tm). - WS doesn't support natively RPC as «function call + return value» - PUB/SUB is also nice to have, especially since it's cluster-aware. > - Direct browser to browser communication. There is a router and that is all, you don't have to setup your own (cluster aware) dispatch logic. edit: this might be helpful http://wamp.ws/why/ http://wamp.ws/why/