NoSQL Question: Download NoSQL PDF
Tell me what are the pros and cons of Graph database?
Answer:
Pros
a) Graph databases seem to be tailor-made for networking applications. The
prototypical example is a social network, where nodes represent users who have various kinds of relationships to each other. Modeling this kind of data using any of the other styles is often a tough fit, but a graph database would accept it with relish.
b) They are also perfect matches for an object-oriented system.
Cons
a) Because of the high degree of interconnectedness between nodes, graph
databases are generally not suitable for network partitioning.
b) Graph databases don’t scale out well.
a) Graph databases seem to be tailor-made for networking applications. The
prototypical example is a social network, where nodes represent users who have various kinds of relationships to each other. Modeling this kind of data using any of the other styles is often a tough fit, but a graph database would accept it with relish.
b) They are also perfect matches for an object-oriented system.
Cons
a) Because of the high degree of interconnectedness between nodes, graph
databases are generally not suitable for network partitioning.
b) Graph databases don’t scale out well.
| Previous Question | Next Question |
| Explain "Polyglot Persistence" in NoSQL? | Explain the modes of operation that Flume supports? |