Hi,
I added a note to your other question about grpc.
There’s nothing to stop you having both dgo and /graphql working together at once. Indeed that’s what some of our users want GraphQL for → to expose a GraphQL view over a graph where other processes are adding and mutating data.
There’s also no need to have different json fields. You can use aliases as a way of mapping internal values to your types, but also, you can map the GraphQL however you like to internal edge names, so you can have the dgo and GraphQL seeing the same names: see here.