Chapter 22
Triple Store Products
In This Chapter
Documenting relationships
Creating scripts
Running fast graph traversal operations
With two key approaches to managing semantic facts — triple stores with RDF and graph stores — you have a wide variety of functionality to consider. This abundance makes choosing which database to use difficult.
My advice is to follow the queries. Both graph and triple stores are capable in their data models of describing things — subjects or vertices — and their properties and relationships. So, the deciding factor isn’t a list of features; it’s what you want to do with the queries.
Perhaps you want to store a set of facts on related concepts, maybe to drive a product-suggestion engine, or to link disparate data sources or reports, or just to provide a very flexible data model for querying that, unlike other NoSQL databases, includes relationships. In this case, a triple store may well work for you.
In other situations, you may need a graph store. You may need to identify the similarities (or not) between different networks. Perhaps you’re looking for parts of your data that match a known pattern of fraud. Maybe you’re powering a navigation application ...
Get NoSQL For Dummies now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
