I have a greenfield that I’ve always been planning to use dgraph for. I see /graphql now, and that’s even better.
Slash Graphql would be the long-term backend, assuming alpha, beta, and seed stages go well.
Question about alpha-stage work, though:
I need a backend for dev. I’m scared of turning on a “real” /graphql, because it’ll likely be in alpha for quite a while before I can justify the $10/mo.
Which workflow would transition to prod better?
A. develop with dgraph locally, using the official dgo go client.
B. develop with a dummy, generic gql backend.
I’m in a gray area. I’m using go and would like to use the dgo client for full gql±, but I’m really excited about using gql to manage my structures for
A gives me part of that, B gives me part of that, but neither gives me all.