News for hackers. Stuff that matters.

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

Re:Why Google needed to build a graph serving system by taherchhabra on Saturday February 16, 2019 @08:39AM (#19178495)
We are using AWS Neptune in building our marketing analytics product. What I have realized is that it has best of both worlds, the querying power of SQL databases and schemaless functionality like nosql databases.
[ Parent | on HN ]
Re:Why Google needed to build a graph serving system by macawfish on Saturday February 16, 2019 @09:27AM (#19178665)
Whenever I read mention of Neptune, I feel obligated to mention Blazegraph, which Amazon based Neptune on.

As I've shamelessly advertised elsewhere in these comments, Blazegraph is in the early stages of a fork and/or reboot, as Amazon's acquisition severely hampered progress on the open source project.

https://github.com/blazegraph/database/issues/86

[ Parent | on HN ]
Re:Why Google needed to build a graph serving system by mrjn on Saturday February 16, 2019 @11:49AM (#19179466)
Consider Dgraph :-).

https://blog.dgraph.io/post/neptune/

[ Parent | on HN ]
Re:Why Google needed to build a graph serving system by taway483 on Saturday February 16, 2019 @12:14PM (#19179599)
I loved working with Dgraph, but I hate doing system/database administration work.. do you have any plans of providing a hosted solution?
[ Parent | on HN ]
Re:Why Google needed to build a graph serving system by mrjn on Saturday February 16, 2019 @12:57PM (#19179860)
No concrete plans yet, but that's a direction we want to go in.
[ Parent | on HN ]