Graph databases offer a number of advantages over relational databases for storing and querying graph-like data, including:
Performance: Graph databases are typically much faster than relational databases for queries that involve traversing relationships between nodes.
Scalability: Graph databases are more scalable than relational databases for large graphs.
Expressiveness: Graph databases offer a more expressive language for querying graph-like data.
For these reasons, i think recursive queries are not a complete replacement for graph databases.
Note:
The decision of whether to use recursive queries or a graph database depends on the specific needs of your application. If you have a small, simple graph, recursive queries may be a good option. However, if you have a large, complex graph, you may need to introduce a graph database to improve performance and scalability.
Yep totally, I think being pragmatic and listen to business requirements is the best way to deliver something : useful, powerful, resilient and scalable.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Hello @bias
Graph databases offer a number of advantages over relational databases for storing and querying graph-like data, including:
Performance: Graph databases are typically much faster than relational databases for queries that involve traversing relationships between nodes.
Scalability: Graph databases are more scalable than relational databases for large graphs.
Expressiveness: Graph databases offer a more expressive language for querying graph-like data.
For these reasons, i think recursive queries are not a complete replacement for graph databases.
Note:
The decision of whether to use recursive queries or a graph database depends on the specific needs of your application. If you have a small, simple graph, recursive queries may be a good option. However, if you have a large, complex graph, you may need to introduce a graph database to improve performance and scalability.
It seems that Graph database are highly specific, do you think we should always shoot for simplicity first ?
Yeah (personal opinion), for me i always shoot for simplicity first. What about you?
Yep totally, I think being pragmatic and listen to business requirements is the best way to deliver something : useful, powerful, resilient and scalable.