Back in 2017, AllCode became a DataStax Partner. We assist DataStax with implementations of DSE which, from a high-level perspective, consists of the following:
- A high availability, high performance, fault tolerant Data Store based upon Apache Cassandra. The CAP Theorem is a concept that a distributed database system can only have 2 of the 3: Consistency, Availability and Partition Tolerance. Cassandra chooses Availability and Partition Tolerance over Consistency.
- With deep search capabilities, DSE integrates with Apache SOLR for searching rows and for use as secondary indexes.
- To provide deep analytics, DSE integrates with Apache Spark 2.0.x.
- The ability to walk relationships. DSE has a Graph database implementation built on top of Cassandra, inspired by Titan.
DataStax Enterprise is not a Relational Database, but DataStax is designed to behave similar to an RDBMS. This can create confusion at times. For example:
- Instead of being called Structure Query Language (SQL), the query language for DataStax is called Cassandra Query Language(CQL), since the product is built on top of Apache Cassandra.
- Similar to traditional RDBMS databases that have A Read–Eval–Print Loop (REPL) entitled ISQL or T-SQL, DSE has CQLSH for their REPL.
- When you’re interacting with tables within a REPL or application code, you can’t join on tables. Joins are actually prohibited, which means that you need to design your tables differently.
- In addition, your queries have limited grouping and only some aggregation capabilities.