2 ms·
Isn't GraphQL by dgraph just another GraphQL layer on top of the underlying graph database? You could have created a separate project for the GraphQL layer com
by progql 6y ago
Isn't GraphQL by dgraph just another GraphQL layer on top of the underlying graph database?
You could have created a separate project for the GraphQL layer compatible with dgraph and other database. But no, you wanted to enforce your graph database which is not proven for production load.
Hence, it is wrong to claim it being different from Hasura just because you are embedding the GraphQL layer and database into a single binary.
- mrjn 6y agoFounder of Dgraph here > But no, you wanted to enforce your graph database which is not proven for production load. One of our customers, a big brand e-commerce site, is running 20 TBs of data on Dgraph. I wonder what makes you claim "not proven for production load." > Hence, it is wrong to claim it being different from Hasura just because you are embedding the GraphQL layer and database into a single binary. Perhaps you could embed GraphQL layer into Postgres, then change the way Postgres stores data to make it do joins better, make Postgres not require strict schemas and allow major schema changes without any downtime, then add distributed transactions, consistent replication, fault tolerance to it; and then yes, it might be close.
- progql 6y agohttps://discuss.nebula-graph.io/t/benchmarking-the-mainstream-open-source-distributed-graph-databases-at-meituan-nebula-graph-vs-dgraph-vs-hugegraph/715 https://discuss.nebula-graph.io/t/benchmarking-the-mainstrea...