DBMS > EJDB vs. MarkLogic vs. TimesTen vs. Yanza

System Properties Comparison EJDB vs. MarkLogic vs. TimesTen vs. Yanza

Please select another system to include it in the comparison.

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)

Operational and transactional Enterprise NoSQL database

In-Memory RDBMS compatible to Oracle

Time Series DBMS for IoT Applications

Primary database model

Document store

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	5.92
Rank	#58	Overall
	#10	Document stores
	#1	Native XML DBMS
	#1	RDF stores
	#6	Search engines

Score	1.31
Rank	#163	Overall
	#74	Relational DBMS

Website

github.com/Softmotions/ejdb

www.marklogic.com

www.oracle.com/database/technologies/related/timesten.html

yanza.com

Technical documentation

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

docs.marklogic.com

docs.oracle.com/database/timesten-18.1

Developer

Softmotions

MarkLogic Corp.

Oracle, TimesTen Performance Software, HP

originally founded in HP Labs it was acquired by Oracle in 2005

Yanza

Initial release

2012

2001

1998

2015

Current release

11.0, December 2022

11 Release 2 (11.2.2.8.0)

License

Commercial or Open Source

Open Source

GPLv2

commercial

restricted free version is available

commercial

free version available

Cloud-based only

Only available as a cloud service

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

Linux
OS X
Windows

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

Windows

Data scheme

schema-free

Schema can be enforced

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

Secondary indexes

yes

SQL

Support of SQL

yes

SQL92

yes

APIs and other access methods

in-process shared library

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

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

HTTP API

Supported programming languages

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

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

C
C++
Java
PL/SQL

any language that supports HTTP calls

Server-side scripts

Stored procedures

yes

via XQuery or JavaScript

PL/SQL

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

Multi-source replication
Source-replica replication

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

Immediate Consistency or Eventual Consistency depending on configuration

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

Durability

Support for making data persistent

yes

by means of logfiles and checkpoints

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes, with Range Indexes

yes

User concepts

Access control

Role-based access control at the document and subdocument levels

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.

More resources

Recent citations in the news

MarkLogic “The NoSQL Database”. In the MarkLogic Query Console, you can… | by Abhay Srivastava | Apr, 2024
23 April 2024, Medium

ABN AMRO Moves Progress-Powered Credit Store App to Azure Cloud; Achieves 40% Faster Data Processing, Lower ...
12 March 2024, GlobeNewswire

Seven Quick Steps to Setting Up MarkLogic Server in Kubernetes
1 February 2024, biplatform.nl

Progress's $355m move for MarkLogic sets the tone for 2023
4 January 2023, The Stack

Progress to acquire PE-backed data platform MarkLogic for $355m
4 January 2023, PE Hub

provided by Google News

In-memory databases with Emulex Gen 7
25 October 2023, Broadcom Inc.

provided by Google News

Share this page