DBMS > BigObject vs. EJDB vs. Greenplum vs. MySQL

System Properties Comparison BigObject vs. EJDB vs. Greenplum vs. MySQL

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Analytic DBMS for real-time computations and queries

Embeddable document-store database library with JSON representation of queries (in MongoDB style)

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

Primary database model

Relational DBMS

a hierachical model (tree) can be imposed

Document store

Relational DBMS

Key/Value like access via memcached API

Secondary database models

Document store
Spatial DBMS

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

Score	0.13
Rank	#333	Overall
	#147	Relational DBMS

Score	0.27
Rank	#297	Overall
	#44	Document stores

Score	8.37
Rank	#48	Overall
	#30	Relational DBMS

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Website

bigobject.io

github.com/Softmotions/ejdb

greenplum.org

www.mysql.com

Technical documentation

docs.bigobject.io

github.com/Softmotions/ejdb/blob/master/README.md

docs.greenplum.org

dev.mysql.com/doc

Developer

BigObject, Inc.

Softmotions

Pivotal Software Inc.

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

2015

2012

2005

1995

Current release

7.0.0, September 2023

8.4.0, April 2024

License

Commercial or Open Source

commercial

free community edition available

Open Source

GPLv2

Open Source

Apache 2.0

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

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.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

C and C++

Server operating systems

Linux

distributed as a docker-image
OS X

distributed as a docker-image (boot2docker)
Windows

distributed as a docker-image (boot2docker)

server-less

Linux

FreeBSD
Linux
OS X
Solaris
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

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

SQL-like DML and DDL statements

yes

with proprietary extensions

APIs and other access methods

fluentd
ODBC
RESTful HTTP API

in-process shared library

JDBC
ODBC

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

Actionscript
C
C#
C++
Go
Java
JavaScript (Node.js)
Lua
Objective-C
Pike
Python
Ruby

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

Server-side scripts

Stored procedures

Lua

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Replication methods

Methods for redundantly storing data on multiple nodes

none

Source-replica replication

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Foreign keys

Referential integrity

yes

automatically between fact table and dimension tables

typically not needed, however similar functionality with collection joins possible

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

Read/write lock on objects (tables, trees)

yes

Read/Write Locking

yes

table locks or row locks depending on storage engine

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

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.