Hi, thanks for the question. I hope these points cover what you want to know. If not, happy to talk more.
At the moment we are only exposing GraphQL over HTTP, but GraphQL± over both HTTP and gRPC.
I think it would be great to expose GraphQL over gRPC. We’ve talked about that a few times internally, but don’t currently have any concrete plans.
dgo is really a Dgraph client. A GraphQL client would probably look a bit different - take out transactions and other Dgraph specific featurs, and add some features that come from the typing in GraphQL. Again it’s a thing we’ve talked about - e.g. wouldn’t it be great if Dgraph had the best golang client libraries for GraphQL - but not something we have a specific plan about at the moment.
You can also use both GraphQL± (for example with dgo) and GraphQL on the same underlying Dgraph instance, so mixing up how you access it depending on the usecase is also possible.