4 ms·
I wonder how this stacks up against a dedicated graph database like Neo4J. Are arbitray-depth graph queries a design goal, or are the nested results just for o
by scribu 7y ago
I wonder how this stacks up against a dedicated graph database like Neo4J.
Are arbitray-depth graph queries a design goal, or are the nested results just for optimizing network traffic?
- 1st1 7y agoEdgeDB is not a graph database, i.e. we didn't build it for traversing super deep schemaless graphs. On the contrary, we optimized it for the kind of applications that are usually built with relational or document databases. Those scenarios frequently involve a relatively complex schema with queries that fetch hierarchies of objects 2-3 levels deep. Doing that efficiently in SQL or NoSQL isn't as simple as it sounds (and the blog post makes a point about that). That said, I expect EdgeDB to perform on par with neo4j on moderately deep object hierarchies. We also plan to add support for recursive queries at some point, although it's not a priority right now.
- scribu 7y agoThanks for the answer. > queries that fetch hierarchies of objects 2-3 levels deep [...] efficiently in SQL or NoSQL isn't as simple as it sounds It doesn't sound simple and it isn't simple. :-)