Authentication is working quite well but involves a lot of manual work right now. Ex: for django you need to create an auth microservice calling django.contrib

Authentication is working quite well but involves a lot of manual work right now. Ex: for django you need to create an auth microservice calling django.contrib.auth authenticate function. Now as for pub/sub, I use uuid to namespace messages and rpc call to fetch the namespace if i want to limit their access. It's imperfect but you have the same issue with redis or bare socket.js. However, last year tavendo added meta events and rpc allowing you to react to sub and control them from the api, so you can roll the policy you want. Again, manual work. Hence the framework I wish we had. The thing is, tavendo targets IoT with crossbar and is developping it's acticity for the factories and office automation. If we want a mature web solution, somebody will have to code it.