Chapter 5. Exploring Neighborhoods in Production
When you use DataStax Graph, you are working with graph data in Cassandra. And if you have been following along and executing the implementation details from the last two chapters, you have already been using it.
The paradigm shift from working with a traditional database to working with Apache Cassandra is that we write our data according to how we are going to read it.
To illustrate how we apply this, the examples in Chapters 3 and 4 used but skipped over fundamental topics of working with graph data in Apache Cassandra. Concepts like edge direction and partition key design are fundamental to building a production-quality, scalable, and distributed graph data model.
We are going to dig deeply into the topics of distributed data to set you up for a successful use of distributed graph technology within your production stack.
Recall that we mentioned at the end of Chapter 4 that we purposely set up some traps. Our example built up the schema shown in Figure 5-1 and aimed to use queries like we have in Example 5-1.
Figure 5-1. The developmental data model for a graph-based implementation of a C360 application from the previous chapter
We need to connect two concepts together so you can see the whole picture. First, all of our queries have used the development traversal source dev.V(). The development traversal source in DataStax ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access