DBMS > EJDB vs. Greenplum vs. MySQL vs. PouchDB

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

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

JavaScript DBMS with an API inspired by CouchDB

Primary database model

Document store

Relational DBMS

Key/Value like access via memcached API

Document store

Secondary database models

Document store
Spatial DBMS

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

Score	0.31
Rank	#296	Overall
	#44	Document stores

Score	8.08
Rank	#48	Overall
	#31	Relational DBMS

Score	1061.34
Rank	#2	Overall
	#2	Relational DBMS

Score	2.34
Rank	#112	Overall
	#21	Document stores

Website

github.com/Softmotions/ejdb

greenplum.org

www.mysql.com

pouchdb.com

Technical documentation

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

docs.greenplum.org

dev.mysql.com/doc

pouchdb.com/guides

Developer

Softmotions

Pivotal Software Inc.

Oracle

since 2010, originally MySQL AB, then Sun

Apache Software Foundation

Initial release

2012

2005

1995

2012

Current release

7.0.0, September 2023

8.4.0, April 2024

7.1.1, June 2019

License

Commercial or Open Source

Open Source

GPLv2

Open Source

Apache 2.0

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

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++

JavaScript

Server operating systems

server-less

Linux

FreeBSD
Linux
OS X
Solaris
Windows

server-less, requires a JavaScript environment (browser, Node.js)

Data scheme

schema-free

yes

schema-free

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

via views

SQL

Support of SQL

yes

with proprietary extensions

APIs and other access methods

in-process shared library

JDBC
ODBC

ADO.NET
JDBC
ODBC
Proprietary native API

HTTP REST

only for PouchDB Server
JavaScript 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

JavaScript

Server-side scripts

Stored procedures

yes

proprietary syntax

View functions in JavaScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

with a proxy-based framework, named couchdb-lounge

Replication methods

Methods for redundantly storing data on multiple nodes

none

Source-replica replication

Multi-source replication
Source-replica replication

Multi-source replication

also with CouchDB databases
Source-replica replication

also with CouchDB databases

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

Foreign keys

Referential integrity

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 Locking

yes

table locks or row locks depending on storage engine

Durability

Support for making data persistent

yes

by using IndexedDB, WebSQL or LevelDB as backend

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.