Database Reference
In-Depth Information
• To store and update various web page metrics and counters
Graph databases
are intended for use cases such as networks, where there are
items (people or web page links) and relationships between these items. While it
is possible to store graphs such as trees in a relational database, it often becomes
cumbersome to navigate, scale, and add new relationships. Graph databases help
to overcome these possible obstacles and can be optimized to quickly traverse
a graph (move from one item in the network to another item in the network).
Following are examples of graph database implementations:
• Social networks such as Facebook and LinkedIn
• Geospatial applications such as delivery and traffic systems to optimize
the time to reach one or more destinations
Table 10.2
provides a few examples of NoSQL data stores. As is often the case,
the choice of a specific data store should be made based on the functional and
performance requirements. A particular data store may provide exceptional
functionality in one aspect, but that functionality may come at a loss of other
functionality or performance.
Table 10.2
Examples of NoSQL Data Stores
Category Data Store Website
Key/Value Redis
redis.io
Voldemort
www.project-voldemort.com/voldemort
Document CouchDB
couchdb.apache.org
MongoDB
www.mongodb.org
Column family Cassandra
cassandra.apache.org
HBase
Graph
FlockDB
github.com/twitter/flockdb
Neo4j
