DBMS > Cassandra vs. Datomic vs. Greenplum vs. Ignite

System Properties Comparison Cassandra vs. Datomic vs. Greenplum vs. Ignite

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Wide-column store based on ideas of BigTable and DynamoDB

Optimized for write access

Datomic builds on immutable values, supports point-in-time queries and uses 3rd party systems for durability

Analytic Database platform built on PostgreSQL. Full name is Pivotal Greenplum Database

A logical database in Greenplum is an array of individual PostgreSQL databases working together to present a single database image.

Apache Ignite is a memory-centric distributed database, caching, and processing platform for transactional, analytical, and streaming workloads, delivering in-memory speeds at petabyte scale.

Primary database model

Wide column store

Relational DBMS

Key-value store
Relational DBMS

Secondary database models

Vector DBMS

starting with release V5

Document store
Spatial DBMS

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

Score	101.89
Rank	#12	Overall
	#1	Wide column stores

Score	1.59
Rank	#150	Overall
	#69	Relational DBMS

Score	8.37
Rank	#48	Overall
	#30	Relational DBMS

Score	3.16
Rank	#96	Overall
	#15	Key-value stores
	#49	Relational DBMS

Website

Technical documentation

cassandra.apache.org/doc/latest

docs.datomic.com

docs.greenplum.org

apacheignite.readme.io/docs

Developer

Apache Software Foundation

Apache top level project, originally developped by Facebook

Cognitect

Pivotal Software Inc.

Apache Software Foundation

Initial release

2008

2012

2005

2015

Current release

4.1.3, July 2023

1.0.6735, June 2023

7.0.0, September 2023

Apache Ignite 2.6

License

Commercial or Open Source

Open Source

Apache version 2

commercial

limited edition free

Open Source

Apache 2.0

Open Source

Apache 2.0

Cloud-based only

Only available as a cloud service

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, Clojure

C++, Java, .Net

Server operating systems

BSD
Linux
OS X
Windows

All OS with a Java VM

Linux

Linux
OS X
Solaris
Windows

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

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

since Version 4.2

yes

Secondary indexes

restricted

only equality queries, not always the best performing solution

yes

SQL

Support of SQL

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

yes

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

APIs and other access methods

Proprietary protocol

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

RESTful HTTP API

JDBC
ODBC

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

Supported programming languages

C#
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript

Node.js
Perl
PHP
Python
Ruby
Scala

Clojure
Java

C
Java
Perl
Python
R

C#
C++
Java
PHP
Python
Ruby
Scala

Server-side scripts

Stored procedures

yes

Transaction Functions

yes

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

Triggers

yes

By using transaction functions

yes

yes (cache interceptors and events)

Partitioning methods

Methods for storing different data on different nodes

Sharding

no "single point of failure"

none

But extensive use of caching in the application peers

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Representation of geographical distribution of servers is possible

none

But extensive use of caching in the application peers

Source-replica replication

yes (replicated cache)

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

yes (compute grid and hadoop accelerator)

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

can be individually decided for each write operation

Immediate Consistency

Foreign keys

Referential integrity

yes

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

using external storage systems (e.g. Cassandra, DynamoDB, PostgreSQL, Couchbase and others)

yes

In-memory capabilities

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

yes

recommended only for testing and development

yes

User concepts

Access control

Access rights for users can be defined per object

fine grained access rights according to SQL-standard

Security Hooks for custom implementations

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.