As a general rule, I tell my team to think about DSE graph as a graph and how graph schemas and traversals work rather than to start thinking about Cassandra and the underlying technologies like Solr.
There are many examples when mentioning Cassandra leads to questions like "Why can't we implement the same using X database" or "How are the tables structured?"
In general, this adds noise to our conversations and adds confusion to the project as it draws the attention to what I think to be the wrong topic.
In my opinion, I believe that we need to concentrate on the graph to focus on what I believe to be the critical part of the project such as how our relationships are defined, how we build our gremlin queries and how do we need to retrieve our data.
I see the internals of DSE graph (how you store the actual tables in Cassandra, what kind of relationships you build between the internal tables, etc) as a layer of abstraction rather than something I need to focus on, but I also understand that some concepts like partitioning is something that we need to be aware of.
For the average stakeholder, I am doing my best to avoid mentioning Cassandra as it adds the noise explained above, but I also understand that some transparency might be needed
Where should we draw the line? How much should we know about Cassandra before considering an implementation with DSE?
