News for hackers. Stuff that matters.

A comment on Why Google needed to build a graph serving system. Parent comment

Re:Why Google needed to build a graph serving system by mrjn on Saturday February 16, 2019 @12:46PM (#19179790)
One of the TLs was a T7. Got overruled by T8 :-).

As Google is growing, there are many T7s around. So, you really need T8 and above to actually get something out of the door, when it comes to impacting web search.

P.S. Dgraph is Apache license, written in Go/Protobufs/Grpc. Google might have an appetite for that, worth pushing internally. https://github.com/dgraph-io/dgraph

[ Parent | on HN ]
Re:Why Google needed to build a graph serving system by biomcgary on Saturday February 16, 2019 @05:44PM (#19181418)
My understanding is that by default, dgraph query responses are in json. Is it possible to get gRPC responses instead?
[ Parent | on HN ]
Re:Why Google needed to build a graph serving system by mrjn on Saturday February 16, 2019 @07:10PM (#19181791)
Dgraph exposes both HTTP endpoint and gRPC endpoint. All our official clients use the gRPC endpoint, including Go, Java, NodeJS client.

https://docs.dgraph.io/deploy#ports-usage

[ Parent | on HN ]