I have done it in the reverse way: have django act to proxy requests to the node server. That way ypu can use django sessions, authentication, login, admin, et

I have done it in the reverse way: have django act to proxy requests to the node server. That way ypu can use django sessions, authentication, login, admin, etc. The node server just does rendering, and creates client side JS based on data it is given by Django. It took 25 lines of code, yes, but pretty much worth it if you have a long term project like a single app that your company is built around.