DBMS > Greenplum vs. MySQL vs. Newts vs. StarRocks

System Properties Comparison Greenplum vs. MySQL vs. Newts vs. StarRocks

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

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.

Widely used open source RDBMS

Time Series DBMS based on Cassandra

An open source, high-performance columnar analytical database that enables real-time, multi-dimensional, and highly concurrent data analytics

Forked from Apache Doris

Primary database model

Relational DBMS

Key/Value like access via memcached API

Time Series DBMS

Relational DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	7.71
Rank	#46	Overall
	#29	Relational DBMS

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Score	0.00
Rank	#385	Overall
	#40	Time Series DBMS

Score	0.95
Rank	#193	Overall
	#89	Relational DBMS

Website

greenplum.org

www.mysql.com

opennms.github.io/newts

www.starrocks.io

Technical documentation

docs.greenplum.org

dev.mysql.com/doc

github.com/OpenNMS/newts/wiki

docs.starrocks.io/en-us/latest/introduction/StarRocks_intro

Developer

Pivotal Software Inc.

Oracle

since 2010, originally MySQL AB, then Sun

OpenNMS Group

The Linux Foundation

since Feb 2023

Initial release

2005

1995

2014

2020

Current release

7.0.0, September 2023

9.0.0, July 2024

3.3, June 2024

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

Apache 2.0

Open Source

Apache Version 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.

Implementation language

C and C++

Java

C++, Java

Server operating systems

Linux

FreeBSD
Linux
OS X
Solaris
Windows

Linux
OS X
Windows

Linux

Data scheme

yes

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

yes

SQL

Support of SQL

yes

with proprietary extensions

yes

APIs and other access methods

JDBC
ODBC

ADO.NET
JDBC
ODBC
Proprietary native API

HTTP REST
Java API

JDBC
MySQL protocol

Supported programming languages

C
Java
Perl
Python
R

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

Java

Server-side scripts

Stored procedures

yes

proprietary syntax

user defined functions

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

based on Cassandra

horizontal partitioning (by range and hash)

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Multi-source replication
Source-replica replication

selectable replication factor

based on Cassandra

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

based on Cassandra
Immediate Consistency

based on Cassandra

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

not for MyISAM storage engine

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

Role based access control and fine grained access rights

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.