DBMS > EJDB vs. IBM Db2 warehouse vs. MarkLogic vs. SQLite vs. Yanza

System Properties Comparison EJDB vs. IBM Db2 warehouse vs. MarkLogic vs. SQLite vs. Yanza

Editorial information provided by DB-Engines

Name

Yanza seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

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

Cloud-based data warehousing service

Operational and transactional Enterprise NoSQL database

Widely used embeddable, in-process RDBMS

Time Series DBMS for IoT Applications

Primary database model

Document store

Relational DBMS

Document store
Native XML DBMS
RDF store

as of version 7
Search engine

Relational DBMS

Time Series DBMS

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

Score	0.27
Rank	#297	Overall
	#44	Document stores

Score	1.30
Rank	#164	Overall
	#75	Relational DBMS

Score	5.92
Rank	#58	Overall
	#10	Document stores
	#1	Native XML DBMS
	#1	RDF stores
	#6	Search engines

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

github.com/Softmotions/ejdb

www.ibm.com/products/db2/warehouse

www.marklogic.com

www.sqlite.org

yanza.com

Technical documentation

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

docs.marklogic.com

www.sqlite.org/docs.html

Developer

Softmotions

IBM

MarkLogic Corp.

Dwayne Richard Hipp

Yanza

Initial release

2012

2014

2001

2000

2015

Current release

11.0, December 2022

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

Open Source

GPLv2

commercial

restricted free version is available

Open Source

Public Domain

commercial

free version available

Cloud-based only

Only available as a cloud service

yes

but mainly used as a service provided by Yanza

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

C++

Server operating systems

server-less

hosted

Linux
OS X
Windows

server-less

Windows

Data scheme

schema-free

yes

schema-free

Schema can be enforced

yes

dynamic column types

schema-free

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

yes

not rigid because of 'dynamic typing' concept.

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.

Import/export of XML data possible

yes

Secondary indexes

yes

SQL

Support of SQL

yes

SQL92

yes

SQL-92 is not fully supported

APIs and other access methods

in-process shared library

.NET Client API
JDBC
ODBC
OLE DB

Java API
Node.js Client API
ODBC
proprietary Optic API

Proprietary Query API, introduced with version 9
RESTful HTTP API
SPARQL
WebDAV
XDBC
XQuery
XSLT

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

HTTP API

Supported programming languages

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

Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby

C
C#
C++
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

any language that supports HTTP calls

Server-side scripts

Stored procedures

PL/SQL, SQL PL

yes

via XQuery or JavaScript

Triggers

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via Hadoop Connector, HDFS Direct Access and in-database MapReduce jobs

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

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

can act as a resource manager in an XA/JTA transaction

ACID

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

yes

via file-system locks

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

yes, with Range Indexes

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Role-based access control at the document and subdocument levels

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.