DBMS > EJDB vs. Greenplum vs. LeanXcale vs. mSQL vs. OrigoDB

System Properties Comparison EJDB vs. Greenplum vs. LeanXcale vs. mSQL vs. OrigoDB

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.

A highly scalable full ACID SQL database with fast NoSQL data ingestion and GIS capabilities

mSQL (Mini SQL) is a simple and lightweight RDBMS

A fully ACID in-memory object graph database

Primary database model

Document store

Relational DBMS

Key-value store
Relational DBMS

Relational DBMS

Document store
Object oriented DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	0.27
Rank	#297	Overall
	#44	Document stores

Score	8.37
Rank	#48	Overall
	#30	Relational DBMS

Score	0.29
Rank	#291	Overall
	#41	Key-value stores
	#132	Relational DBMS

Score	1.27
Rank	#167	Overall
	#77	Relational DBMS

Score	0.00
Rank	#383	Overall
	#53	Document stores
	#20	Object oriented DBMS

Website

github.com/Softmotions/ejdb

greenplum.org

www.leanxcale.com

hughestech.com.au/products/msql

origodb.com

Technical documentation

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

docs.greenplum.org

origodb.com/docs

Developer

Softmotions

Pivotal Software Inc.

LeanXcale

Hughes Technologies

Robert Friberg et al

Initial release

2012

2005

2015

1994

2009

under the name LiveDB

Current release

7.0.0, September 2023

4.4, October 2021

License

Commercial or Open Source

Open Source

GPLv2

Open Source

Apache 2.0

commercial

free licenses can be provided

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.

Implementation language

Server operating systems

server-less

Linux

AIX
HP-UX
Linux
OS X
Solaris SPARC/x86
Windows

Linux
Windows

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

yes

User defined using .NET types and collections

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

can be achieved using .NET

Secondary indexes

yes

SQL

Support of SQL

yes

through Apache Derby

A subset of ANSI SQL is implemented

no subqueries, aggregate functions, views, foreign keys, triggers

APIs and other access methods

in-process shared library

JDBC
ODBC

JDBC
Kafka Connector
ODBC
proprietary key/value interface
Spark Connector

JDBC
ODBC

.NET Client API
HTTP API
LINQ

Supported programming languages

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

C
Java
Perl
Python
R

C
Java
Scala

C
C++
Delphi
Java
Perl
PHP
Tcl

.Net

Server-side scripts

Stored procedures

yes

Triggers

yes

Domain Events

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

horizontal partitioning

client side managed; servers are not synchronized

Replication methods

Methods for redundantly storing data on multiple nodes

none

Source-replica replication

none

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

none

Foreign keys

Referential integrity

typically not needed, however similar functionality with collection joins possible

yes

depending on model

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

yes

Durability

Support for making data persistent

yes

Write ahead log

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

Role based authorization

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

Recent citations in the news

VMware Greenplum on AWS: Parallel Postgres for Enterprise Analytics at Scale | Amazon Web Services
9 September 2019, AWS Blog

1. Introducing the Greenplum Database - Data Warehousing with Greenplum [Book]
6 December 2018, O'Reilly Media

RSA: EMC integrates Hadoop with Greenplum database
26 February 2013, DatacenterDynamics

Greenplum 6 ventures outside the analytic box | ZDNET
19 March 2019, ZDNet

Greenplum 6 review: Jack of all trades, master of some
7 November 2019, InfoWorld

provided by Google News

Combining operational and analytical databases in a single platform
26 May 2017, Cordis News

provided by Google News

Make Your MySQL Server More Secure With These 7 Steps - MUO
1 December 2022, MakeUseOf

Writing a Web Service in Perl
9 July 2003, PCQuest

Higher Education PS rules out ghost students before PAC - Zambia
29 November 2018, diggers.news

provided by Google News

Share this page