DBMS > Apache Phoenix vs. Cassandra vs. Geode

System Properties Comparison Apache Phoenix vs. Cassandra vs. Geode

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A scale-out RDBMS with evolutionary schema built on Apache HBase

Wide-column store based on ideas of BigTable and DynamoDB

Optimized for write access

Geode is a distributed data container, pooling memory, CPU, network resources, and optionally local disk across multiple processes

Primary database model

Relational DBMS

Wide column store

Key-value store

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

Score	3.01
Rank	#103	Overall
	#52	Relational DBMS

Score	118.01
Rank	#11	Overall
	#1	Wide column stores

Score	1.77
Rank	#134	Overall
	#26	Key-value stores

Website

phoenix.apache.org

cassandra.apache.org

geode.apache.org

Technical documentation

phoenix.apache.org

cassandra.apache.org/doc/latest

geode.apache.org/docs

Developer

Apache Software Foundation

Apache top level project, originally developped by Facebook

Originally developed by Gemstone. They outsourced the project to Apache in 2015 but still deliver a commercial version as Gemfire.

Initial release

2014

2008

2002

Current release

5.0-HBase2, July 2018 and 4.15-HBase1, December 2019

4.0.4, May 2022

1.1, February 2017

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

Apache version 2

Open Source

Apache Version 2; commercial licenses available as Gemfire

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

Server operating systems

Linux
Unix
Windows

BSD
Linux
OS X
Windows

All OS with a Java VM

the JDK (8 or later) is also required

Data scheme

yes

late-bound, schema-on-read capabilities

schema-free

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.

Secondary indexes

yes

restricted

only equality queries, not always the best performing solution

SQL

Support of SQL

yes

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

SQL-like query language (OQL)

APIs and other access methods

JDBC

Proprietary protocol

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

Java Client API
Memcached protocol
RESTful HTTP API

Supported programming languages

C
C#
C++
Go
Groovy
Java
PHP
Python
Scala

C#
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript

Node.js
Perl
PHP
Python
Ruby
Scala

.Net
All JVM based languages
C++
Groovy
Java
Scala

Server-side scripts

Stored procedures

user defined functions

Triggers

yes

Cache Event Listeners

Partitioning methods

Methods for storing different data on different nodes

Sharding

no "single point of failure"

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

selectable replication factor

Representation of geographical distribution of servers is possible

Multi-source replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Hadoop integration

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency

Eventual Consistency
Immediate Consistency

can be individually decided for each write operation

Eventual Consistency

Foreign keys

Referential integrity

Transaction concepts

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

ACID

Atomicity and isolation are supported for single operations

yes, on a single node

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 Control Lists (using HBase ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC, multi-tenancy

Access rights for users can be defined per object

Access rights per client and object definable

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

News

5 Ways to Develop Faster and Easier with Apache Cassandra on AWS
13 May 2022

Why a Cloud-Native Database Must Run on K8s
12 May 2022

Introduction to Apache Cassandra - the “Lamborghini” of the NoSQL World
11 May 2022

Cassandra Myth Busters: How Hard Is It to Run Cassandra on Kubernetes?
10 May 2022

3 Ways LakeFS Can Benefit Your Data Lake and Eliminate the Fear of Data Loss
5 May 2022

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.