use only the golang server, both for graphql and frontend
skariel opened this issue · comments
why is the nodejs server needed when we have a golang server?
Hi @skariel
You are absolutely right, there is no real reason to use a NodeJS server.
This repo was originally created with the intention to show the parallels between the original relay-starter-kit that was first published, which was designed for the NodeJS community and was being referenced by a lot of articles back then.
It seems that having a GraphQL server on NodeJS is what most developers are initially exposed to, since the reference implementation that's published by Facebook was written for NodeJS. I was hoping back then that, together with the graphql-go library that I'm contributing to, this repo would help with the transition to having a GraphQL server on Go.
Personally I think an app server written in Go that serves both the NodeJS app and GraphQL requests, is way more performant than an app server written in NodeJS.
I have since have used a different stack for my Go/Golang + GraphQL + Relay + React + ES6/ES2015 + Webpack + Babel, where the app server is fully Go. I have deployed a small scale (<1000 active users) project on that stack and I'm monitoring the infrastructure. (It has been promising, so far).
I might clean it up and publish that when I can find time to plan for it.
Thanks for bringing this up!
Cheers!
"I have since have used a different stack for my Go/Golang + GraphQL + Relay + React + ES6/ES2015 + Webpack + Babel, where the app server is fully Go"
I would be very interested... ;)
Me as well!