DBMS > EJDB vs. HarperDB vs. MySQL vs. Sequoiadb

System Properties Comparison EJDB vs. HarperDB vs. MySQL vs. Sequoiadb

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)

Ultra-low latency distributed database with an intuitive REST API supporting NoSQL and SQL (including joins). Deployment of functions and databases simultaneously with a consolidated node-level architecture.

Widely used open source RDBMS

NewSQL database with distributed OLTP and SQL

Primary database model

Document store

Relational DBMS

Key/Value like access via memcached API

Document store
Relational DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	0.30
Rank	#294	Overall
	#44	Document stores

Score	0.55
Rank	#252	Overall
	#38	Document stores

Score	1087.72
Rank	#2	Overall
	#2	Relational DBMS

Score	0.48
Rank	#260	Overall
	#41	Document stores
	#121	Relational DBMS

Website

github.com/Softmotions/ejdb

www.harperdb.io

www.mysql.com

www.sequoiadb.com

Technical documentation

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

docs.harperdb.io/docs

dev.mysql.com/doc

www.sequoiadb.com/en/index.php?m=Files&a=index

Developer

Softmotions

HarperDB

Oracle

since 2010, originally MySQL AB, then Sun

Sequoiadb Ltd.

Initial release

2012

2017

1995

2013

Current release

3.1, August 2021

8.3.0, January 2024

License

Commercial or Open Source

Open Source

GPLv2

commercial

free community edition available

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

Server: AGPL; Client: Apache V2

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

Node.js

C and C++

C++

Server operating systems

server-less

Linux
OS X

FreeBSD
Linux
OS X
Solaris
Windows

Linux

Data scheme

schema-free

dynamic schema

yes

schema-free

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

yes

JSON data types

yes

oid, date, timestamp, binary, regex

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

Secondary indexes

yes

SQL

Support of SQL

SQL-like data manipulation statements

yes

with proprietary extensions

SQL-like query language

APIs and other access methods

in-process shared library

JDBC
ODBC
React Hooks
RESTful HTTP/JSON API
WebSocket

ADO.NET
JDBC
ODBC
Proprietary native API

proprietary protocol using JSON

Supported programming languages

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

.Net
C
C#
C++
ColdFusion
D
Dart
Delphi
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Lisp
MatLab
Objective C
Perl
PHP
PowerShell
Prolog
Python
R
Ruby
Rust
Scala
Swift

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

.Net
C++
Java
PHP
Python

Server-side scripts

Stored procedures

Custom Functions

since release 3.1

yes

proprietary syntax

JavaScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

A table resides as a whole on one (or more) nodes in a cluster

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

the nodes on which a table resides can be defined

Multi-source replication
Source-replica replication

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

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

Atomic execution of specific operations

ACID

not for MyISAM storage engine

Document is locked during a transaction

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

yes

table locks or row locks depending on storage engine

yes

Durability

Support for making data persistent

yes

yes, using LMDB

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

Access rights for users and roles

Users with fine-grained authorization concept

no user groups or roles

simple password-based access control

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.