DBMS > ArcadeDB vs. EJDB vs. Machbase Neo vs. Postgres-XL

System Properties Comparison ArcadeDB vs. EJDB vs. Machbase Neo vs. Postgres-XL

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Fast and scalable multi-model DBMS, originally forked from OrientDB but most of the code has been rewritten

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

TimeSeries DBMS for AIoT and BigData

Based on PostgreSQL enhanced with MPP and write-scale-out cluster features

Primary database model

Document store
Graph DBMS
Key-value store
Time Series DBMS

in next version

Document store

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	0.10
Rank	#358	Overall
	#48	Document stores
	#38	Graph DBMS
	#52	Key-value stores
	#35	Time Series DBMS

Score	0.31
Rank	#296	Overall
	#44	Document stores

Score	0.17
Rank	#337	Overall
	#30	Time Series DBMS

Score	0.53
Rank	#254	Overall
	#117	Relational DBMS

Website

arcadedb.com

github.com/Softmotions/ejdb

machbase.com

www.postgres-xl.org

Technical documentation

docs.arcadedb.com

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

machbase.com/dbms

www.postgres-xl.org/documentation

Developer

Arcade Data

Softmotions

Machbase

Initial release

2021

2012

2013

2014

since 2012, originally named StormDB

Current release

September 2021

V8.0, August 2023

10 R1, October 2018

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

GPLv2

commercial

free test version available

Open Source

Mozilla public license

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

Java

Server operating systems

All OS with a Java VM

server-less

Linux
macOS
Windows

Linux
macOS

Data scheme

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

XML type, but no XML query functionality

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language, no joins

SQL-like query language

yes

distributed, parallel query execution

APIs and other access methods

JDBC
MongoDB API
OpenCypher
PostgreSQL wire protocol
Redis API
RESTful HTTP/JSON API
TinkerPop Gremlin

in-process shared library

gRPC
HTTP REST
JDBC
MQTT (Message Queue Telemetry Transport)
ODBC

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

Supported programming languages

Java

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

C
C#
C++
Go
Java
JavaScript
PHP

via ODBC
Python
R

via ODBC
Scala

.Net
C
C++
Delphi
Erlang
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

Server-side scripts

Stored procedures

user defined functions

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

none

selectable replication factor

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

relationship in graphs

typically not needed, however similar functionality with collection joins possible

yes

Transaction concepts

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

ACID

MVCC

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

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

volatile and lookup table

User concepts

Access control

simple password-based access control

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.

Related products and services

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

Share this page