I've done almost exactly the kind of thing described in article for a couple millions of rows. It broke down when I needed to find "friends of friends" of depth 6.
None of the optimizations I could come up with helped. Neither did Apache Age.
Maybe I'm just not skilled enough to handle such a workload with Postgres. But Neo4j handled it easily
Maybe I'm just not skilled enough to handle such a workload with Postgres. But Neo4j handled it easily