DBMS > Databend vs. Greenplum vs. Riak KV vs. SAP HANA vs. YottaDB

System Properties Comparison Databend vs. Greenplum vs. Riak KV vs. SAP HANA vs. YottaDB

Editorial information provided by DB-Engines

Name

Description

An open-source, elastic, and workload-aware cloud data warehouse designed to meet businesses' massive-scale analytics needs at low cost and with low complexity

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.

Distributed, fault tolerant key-value store

In-memory, column based data store. Available as appliance or cloud service

A fast and solid embedded Key-value store

Primary database model

Relational DBMS

Key-value store

with links between data sets and object tags for the creation of secondary indexes

Relational DBMS

Key-value store

Secondary database models

Document store
Spatial DBMS

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

Relational DBMS

using the Octo plugin

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

Score	0.34
Rank	#283	Overall
	#130	Relational DBMS

Score	8.08
Rank	#48	Overall
	#31	Relational DBMS

Score	4.01
Rank	#79	Overall
	#9	Key-value stores

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Score	0.28
Rank	#306	Overall
	#44	Key-value stores

Website

github.com/datafuselabs/databend
www.databend.com

greenplum.org

www.sap.com/products/hana.html

yottadb.com

Technical documentation

docs.databend.com

docs.greenplum.org

www.tiot.jp/riak-docs/riak/kv/latest

help.sap.com/hana

yottadb.com/resources/documentation

Developer

Databend Labs

Pivotal Software Inc.

OpenSource, formerly Basho Technologies

SAP

YottaDB, LLC

Initial release

2021

2005

2009

2010

2001

Current release

1.0.59, April 2023

7.0.0, September 2023

3.2.0, December 2022

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

Apache 2.0

Open Source

Apache version 2, commercial enterprise edition

commercial

Open Source

AGPL 3.0

Cloud-based only

Only available as a cloud service

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

Rust

Erlang

Server operating systems

hosted
Linux
macOS

Linux

Linux
OS X

Appliance or cloud-service

Docker
Linux

Data scheme

yes

schema-free

yes

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

Secondary indexes

yes

restricted

yes

SQL

Support of SQL

yes

by using the Octo plugin

APIs and other access methods

CLI Client
JDBC
RESTful HTTP API

JDBC
ODBC

HTTP API
Native Erlang Interface

JDBC
ODBC

PostgreSQL wire protocol

using the Octo plugin
Proprietary protocol

Supported programming languages

Go
Java
JavaScript (Node.js)
Python
Rust

C
Java
Perl
Python
R

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

C
Go
JavaScript (Node.js)
Lua
M
Perl
Python
Rust

Server-side scripts

Stored procedures

yes

Erlang

SQLScript, R

Triggers

yes

pre-commit hooks and post-commit hooks

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

no "single point of failure"

yes

Replication methods

Methods for redundantly storing data on multiple nodes

none

Source-replica replication

selectable replication factor

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

links between data sets can be stored

yes

Transaction concepts

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

yes

ACID

optimistic locking

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

Users with fine-grained authorization concept, user roles

fine grained access rights according to SQL-standard

yes, using Riak Security

yes

Users and groups based on OS-security mechanisms

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.