Django channel is a way to mitigate django limitations. In that sense it does work but it doesn't do a 10th of what crossbar do. Channels let you do websocket,

Django channel is a way to mitigate django limitations. In that sense it does work but it doesn't do a 10th of what crossbar do. Channels let you do websocket, but crossbar add a standardizes a protocol on top of it for rpc and pub sub. It propagate errors for you, allow wild cards in routing, load balancing for rpc, and allow php, c#, js and python code to talk to each others transparently. But the best feature is: crossbar route all messages for you and clients don't need to know about other clients, only about the crossbar. It takes a time to realize how important this is, but it changes the whole architecture of your app. Channels are basically only non blocking data pipes for django, with one for websocket. Useful, but nowhere as powerful. I've made a living with django for years and love the framework, but channels feel like a hack to me. I hope for a django 2.0 with backed in async/await.