DBMS > Cassandra vs. GridGain vs. Rockset vs. Teradata Aster

System Properties Comparison Cassandra vs. GridGain vs. Rockset vs. Teradata Aster

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Teradata Aster has been integrated into other Teradata systems and therefore will be removed from the DB-Engines ranking.

Description

Wide-column store based on ideas of BigTable and DynamoDB

Optimized for write access

GridGain is an in-memory computing platform, built on Apache Ignite

A scalable, reliable search and analytics service in the cloud, built on RocksDB

Platform for big data analytics on multistructured data sources and types

Primary database model

Wide column store

Key-value store
Relational DBMS

Document store

Relational DBMS

Secondary database models

Vector DBMS

starting with release V5

Relational DBMS
Search engine

DB-Engines Ranking measures the popularity of database management systems
Trend Chart

Score	101.89
Rank	#12	Overall
	#1	Wide column stores

Score	1.47
Rank	#154	Overall
	#26	Key-value stores
	#72	Relational DBMS

Score	0.79
Rank	#211	Overall
	#35	Document stores

Website

cassandra.apache.org

www.gridgain.com

rockset.com

Technical documentation

cassandra.apache.org/doc/latest

www.gridgain.com/docs/index.html

docs.rockset.com

Developer

Apache Software Foundation

Apache top level project, originally developped by Facebook

GridGain Systems, Inc.

Rockset

Teradata

Initial release

2008

2007

2019

2005

Current release

4.1.3, July 2023

GridGain 8.5.1

License

Commercial or Open Source

Open Source

Apache version 2

commercial

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Astra DB: Multi-cloud DBaaS built on Apache Cassandra.

Implementation language

Java

Java, C++, .Net

C++

Server operating systems

BSD
Linux
OS X
Windows

Linux
OS X
Solaris
Windows

hosted

Linux

Data scheme

schema-free

yes

schema-free

Flexible Schema (defined schema, partial schema, schema free)

defined schema within the relational store; partial schema or schema free in the Aster File Store

Typing

predefined data types such as float or date

yes

dynamic typing

yes

XML support

Some form of processing data in XML format, e.g. support for XML data structures, and/or support for XPath, XQuery or XSLT.

yes

ingestion from XML files supported

yes

in Aster File Store

Secondary indexes

restricted

only equality queries, not always the best performing solution

yes

all fields are automatically indexed

yes

SQL

Support of SQL

SQL-like SELECT, DML and DDL statements (CQL)

ANSI-99 for query and DML statements, subset of DDL

Read-only SQL queries, including JOINs

yes

APIs and other access methods

Proprietary protocol

CQL (Cassandra Query Language, an SQL-like language)
Thrift

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

HTTP REST

ADO.NET
JDBC
ODBC
OLE DB

Supported programming languages

C#
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript

Node.js
Perl
PHP
Python
Ruby
Scala

C#
C++
Java
PHP
Python
Ruby
Scala

Go
Java
JavaScript (Node.js)
Python

C
C#
C++
Java
Python
R

Server-side scripts

Stored procedures

yes (compute grid and cache interceptors can be used instead)

R packages

Triggers

yes

yes (cache interceptors and events)

Partitioning methods

Methods for storing different data on different nodes

Sharding

no "single point of failure"

Sharding

Automatic sharding

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Representation of geographical distribution of servers is possible

yes (replicated cache)

yes

Dimension tables are replicated across all nodes in the cluster. The number of replicas for the file store can be configured.

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

yes (compute grid and hadoop accelerator)

yes

SQL Map-Reduce Framework

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

can be individually decided for each write operation

Immediate Consistency

Eventual Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Foreign keys

Referential integrity

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

Atomicity and isolation are supported for single operations

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

User concepts

Access control

Access rights for users can be defined per object

Security Hooks for custom implementations

Access rights for users and organizations can be defined via Rockset console

fine grained access rights according to SQL-standard

More information provided by the system vendor

Specific characteristics

Apache Cassandra is the leading NoSQL, distributed database management system, well...
» more

Competitive advantages

No single point of failure ensures 100% availability . Operational simplicity for...
» more

Typical application scenarios

Internet of Things (IOT), fraud detection applications, recommendation engines, product...
» more

Key customers

Apple, Netflix, Uber, ING,, Intuit,Fidelity, NY Times, Outbrain, BazaarVoice, Best...
» more

Market metrics

Cassandra is used by 40% of the Fortune 100.
» more

Licensing and pricing models

Apache licenseÂ Pricing for commercial distributions provided by DataStax and available...
» more

We invite representatives of system vendors to contact us for updating and extending the system information,
and for displaying vendor-provided information such as key customers, competitive advantages and market metrics.