DBMS > Apache Phoenix vs. Geode vs. Greenplum vs. Snowflake vs. SWC-DB

System Properties Comparison Apache Phoenix vs. Geode vs. Greenplum vs. Snowflake vs. SWC-DB

Editorial information provided by DB-Engines

Name

Description

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

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

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.

Cloud-based data warehousing service for structured and semi-structured data

A high performance, scalable Wide Column DBMS

Primary database model

Secondary database models

Document store
Spatial DBMS

Time Series DBMS

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

Score	2.06
Rank	#123	Overall
	#58	Relational DBMS

Score	1.86
Rank	#134	Overall
	#24	Key-value stores

Score	8.08
Rank	#48	Overall
	#31	Relational DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	0.08
Rank	#364	Overall
	#13	Wide column stores

Website

github.com/kashirin-alex/swc-db
www.swcdb.org

Technical documentation

phoenix.apache.org

geode.apache.org/docs

docs.greenplum.org

docs.snowflake.net/manuals/index.html

Developer

Apache Software Foundation

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

Pivotal Software Inc.

Snowflake Computing Inc.

Alex Kashirin

Initial release

2014

2002

2005

2014

2020

Current release

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

1.1, February 2017

7.0.0, September 2023

0.5, April 2021

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

Apache Version 2; commercial licenses available as Gemfire

Open Source

Apache 2.0

commercial

Open Source

GPL V3

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.

Implementation language

Java

C++

Server operating systems

Linux
Unix
Windows

All OS with a Java VM

the JDK (8 or later) is also required

Linux

hosted

Linux

Data scheme

yes

late-bound, schema-on-read capabilities

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

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.

yes

since Version 4.2

yes

Secondary indexes

yes

SQL

Support of SQL

yes

SQL-like query language (OQL)

yes

SQL-like query language

APIs and other access methods

JDBC

Java Client API
Memcached protocol
RESTful HTTP API

JDBC
ODBC

CLI Client
JDBC
ODBC

Proprietary protocol
Thrift

Supported programming languages

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

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

C
Java
Perl
Python
R

JavaScript (Node.js)
Python

C++

Server-side scripts

Stored procedures

user defined functions

yes

user defined functions

Triggers

yes

Cache Event Listeners

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

Multi-source replication

Source-replica replication

yes

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

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

yes, on a single node

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

Access rights per client and object definable

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept, user roles and pluggable authentication

More information provided by the system vendor

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.