DBMS > Greenplum vs. Immudb vs. PlanetScale vs. Snowflake vs. Yaacomo

System Properties Comparison Greenplum vs. Immudb vs. PlanetScale vs. Snowflake vs. Yaacomo

Editorial information provided by DB-Engines

Name

Yaacomo seems to be discontinued and is removed from the DB-Engines ranking

Description

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.

An open source immutable (append-only) database with cryptographic verification which makes it tamper-resistant and fully auditable.

Scalable, distributed, serverless MySQL database platform built on top of Vitess

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

OpenCL based in-memory RDBMS, designed for efficiently utilizing the hardware via parallel computing

Primary database model

Relational DBMS

Key-value store

Relational DBMS

Secondary database models

Document store
Spatial DBMS

Relational DBMS

Document store
Spatial DBMS

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

Score	8.37
Rank	#48	Overall
	#30	Relational DBMS

Score	0.24
Rank	#305	Overall
	#43	Key-value stores

Score	1.59
Rank	#151	Overall
	#70	Relational DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

greenplum.org

github.com/codenotary/immudb
immudb.io

planetscale.com

www.snowflake.com

yaacomo.com

Technical documentation

docs.greenplum.org

docs.immudb.io

planetscale.com/docs

docs.snowflake.net/manuals/index.html

Developer

Pivotal Software Inc.

Codenotary

PlanetScale

Snowflake Computing Inc.

Q2WEB GmbH

Initial release

2005

2020

2014

2009

Current release

7.0.0, September 2023

1.2.3, April 2022

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

Apache Version 2.0

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.

Implementation language

Server operating systems

Linux

BSD
Linux
macOS
Solaris
Windows
z/OS

Docker
Linux
macOS

hosted

Android
Linux
Windows

Data scheme

yes

schema-free

yes

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

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

yes

SQL

Support of SQL

yes

SQL-like syntax

yes

with proprietary extensions

yes

APIs and other access methods

JDBC
ODBC

gRPC protocol
PostgreSQL wire protocol

ADO.NET
JDBC
MySQL protocol
ODBC

CLI Client
JDBC
ODBC

JDBC
ODBC

Supported programming languages

C
Java
Perl
Python
R

.Net
Go
Java
JavaScript (Node.js)
Python

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

proprietary syntax

user defined functions

Triggers

yes

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Multi-source replication
Source-replica replication

yes

Source-replica replication

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 across shards
Immediate Consistency within a shard

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

Transaction concepts

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

ACID

ACID at shard level

ACID

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

no user groups or roles

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

fine grained access rights according to SQL-standard

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.