Hi Datahub team, by the time of ES as graph db imp...
# getting-started
a
Hi Datahub team, by the time of ES as graph db implementations, did you have some kind of performance comparison between ES as GraphDB and Neo4j? Or the ration of replacing Neo4j with ES is mainly from the consideration of simplicity of tech stack, and possible cost reason (neo4j). I did a quick comparison by comparing the time used of executing
GraphService
for neo4j and es separately, I didn't see there is obviously performance gain if with ES.
l
It was mainly to simplify the tech stack for most people since like you mentioned ES works well enough for the current workload (1-hop queries or multi-hop from a single starting node) cc @green-football-43791
we will still allow pluggability of more sophisticated graph databases for workloads which need multi-source multi-hop queries (those use-cases will come in the future)