Database Reference
In-Depth Information
° They all give up one or more characteristics of the relational database
model in order to benefit it in other places. Different implementations
oftheaggregatestoreswillallowyoutorelaxyourconsistency/
transactional requirements and will give you the benefit of enhanced
(and sometimes, massive) scalability. This, obviously, is no small
thing, if your problem is around scale, of course.
I
DENORMALI E
Z
Aggregate data into documents
RICHER MODEL
Connected structured data
Simple data model
Map-reduce friendly
Expressive power
Fast graph traversals
Relational crossroads, courtesy of Alistair Jones
• On the other side of the crossroads are the graph databases, such as Neo4j.
One could argue that graph databases actually take relational databases:
° One step further, by enhancing the data model with a more granular,
more expressive method for storing data, thereby allowing much
more complex questions to be asked of the database, and effectively,
as we later will see, demining the join bomb.
° Back to its roots, by reusing some of the original ideas of navigational
databases, but of course learning from the lessons of the relational
database world by reducing complexity and facilitating easy
querying capabilities.
Withthatintroductionandclassiicationbehindus,wearenowreadytotakea
closer look at graph databases.
