I've felt the same about the documentation for graphene. It's vary basic. I've also had a struggle using subscriptions with the graphql-ws library. No explanati

I've felt the same about the documentation for graphene. It's vary basic. I've also had a struggle using subscriptions with the graphql-ws library. No explanations of how to actually hook subscriptions to some sort of pubsub system or anything like that. I figured it out enventually on my own but it did feel like I was fighting against he grain by not just using nodejs for the server component and proxying calls to my python services. We have a significant investment in python so it was a question of spending time training backend devs on JS for one service or working out the kinks and having one of us become the expert to help others. I think we got to a point where we are ok with graphene and al. but I can't direct my team towards any decent documentation. I'm basically going to have to write my own cookbook style docs for them. Not a huge deal but I'd say if you have the option I'm not convinced you should go the python route today as the nodejs ecosystem for graphql is much more mature (yet still has a long way to go). I'm pretty sure the GraphQL gains will be worth it in the end but we are all early adopters right now, regardless of stack.