When to use DSE Graph

DSE Graph inherits the benefits of Apache Cassandra as part of the DataStax Enterprise (DSE) database, while adding the ability to adapt to enterprise needs with other models such as graph or JSON data storage.

As an extension of the DSE database, DSE Graph reaps benefits if data is highly connected, revealing depth and breadth of the relationships between entities. DSE Graph uses query optimization that automatically processes as much of the query as possible in parallel, leading to increased performance.

Graph index structures create optimal entry points for queries, before starting a graph traversal. Graph partitioning handles vertices with extreme connectedness to prevent hotspots during the graph traversal.

Use DSE Graph to store data when the following characteristics are required:

  • Comprehensive data model

  • Data is database centric with single query

  • Entities and relationships are queried

  • Application is read heavy

Use the DSE database to store data when the following characteristics are required:

  • Heavy denormalization

  • Data is application centric with multiple queries

  • Individual entities are queried

  • Application is write heavy

Was this helpful?

Give Feedback

How can we improve the documentation?

© 2024 DataStax | Privacy policy | Terms of use

Apache, Apache Cassandra, Cassandra, Apache Tomcat, Tomcat, Apache Lucene, Apache Solr, Apache Hadoop, Hadoop, Apache Pulsar, Pulsar, Apache Spark, Spark, Apache TinkerPop, TinkerPop, Apache Kafka and Kafka are either registered trademarks or trademarks of the Apache Software Foundation or its subsidiaries in Canada, the United States and/or other countries. Kubernetes is the registered trademark of the Linux Foundation.

General Inquiries: +1 (650) 389-6000, info@datastax.com