Welcome!
This depends on the resources you have. Personally I never thought of track this, maybe we should start doing this in benchmarks. You can check out this guy bench GitHub - linuxerwang/dgraph-bench: A benchmark program for dgraph. and in our blog we have some benchmarks too Dgraph Blog - Dgraph Blog e.g Loading close to 1M edges/sec into Dgraph - Dgraph Blog
You can also test with ludicrous mode, and you gonna have astonishing results.
For now, GraphQL don’t support Geo-Spatial queries. You can read this RFC Implementing Geo features in GraphQL
Dgraph wasn’t designed for that.
Not sure what is the point of the question. The docs should say what and where? Your example is the answer?
If you are starting to learn Dgraph you should take our Tour A Tour of Dgraph
The only difference is implicit. One is focused on GraphQL only, the other on Dgraph’s features, operations, and so on.
Not possible, you can make the whole server read-only tho.
Not sure If I got the question. Maybe the answer is https://graphql.dgraph.io/dgraph. If not so, please clarify. BTW, as GraphQL+- is inspired in GraphQL, almost everything is similar between them.
In general, yes, you should handle this with a storage service. You can use https://graphql.dgraph.io/custom/ to do this.
I think so, it Is hard to find good Go Dev, so imagine how hard it is to find Rust dev. Today maybe it is different.
It is in Ratel’s roadmap to support GraphQL queries.
Cheers.