DBMS > EJDB vs. Manticore Search vs. Microsoft Azure Cosmos DB vs. TerminusDB

System Properties Comparison EJDB vs. Manticore Search vs. Microsoft Azure Cosmos DB vs. TerminusDB

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)

Multi-storage database for search, including full-text search.

Globally distributed, horizontally scalable, multi-model database service

Scalable Graph Database platform making enterprise data available by exploiting inferred entities and relationships

Primary database model

Document store

Search engine

Document store
Graph DBMS
Key-value store
Wide column store

Graph DBMS

Secondary database models

Time Series DBMS

using the Manticore Columnar Library

Spatial DBMS

Document store
RDF store

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

Score	0.31
Rank	#296	Overall
	#44	Document stores

Score	0.29
Rank	#302	Overall
	#21	Search engines

Score	27.71
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Score	0.23
Rank	#316	Overall
	#27	Graph DBMS

Website

github.com/Softmotions/ejdb

manticoresearch.com

azure.microsoft.com/services/cosmos-db

terminusdb.com

Technical documentation

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

manual.manticoresearch.com

learn.microsoft.com/azure/cosmos-db

terminusdb.github.io/terminusdb/#

Developer

Softmotions

Manticore Software

Microsoft

DataChemist Ltd.

Initial release

2012

2017

2014

2018

Current release

6.0, February 2023

11.0.0, January 2023

License

Commercial or Open Source

Open Source

GPLv2

Open Source

GPL version 2

commercial

Open Source

GPL V3

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

C++

Prolog, Rust

Server operating systems

server-less

FreeBSD
Linux
macOS
Windows

hosted

Linux

Data scheme

schema-free

Fixed schema

schema-free

yes

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

Int, Bigint, Float, Timestamp, Bit, Int array, Bigint array, JSON, Boolean

yes

JSON types

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.

Can index from XML

Secondary indexes

yes

full-text index on all search fields

yes

All properties auto-indexed by default

SQL

Support of SQL

SQL-like query language

SQL-like query language (WOQL)

APIs and other access methods

in-process shared library

Binary API
RESTful HTTP/JSON API
RESTful HTTP/SQL API
SQL over MySQL

DocumentDB API
Graph API (Gremlin)
MongoDB API
RESTful HTTP API
Table API

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

Supported programming languages

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

Elixir
Go
Java
JavaScript (Node.js)
Perl
PHP
Python

.Net
C#
Java
JavaScript
JavaScript (Node.js)
MongoDB client drivers written for various programming languages
Python

JavaScript
Python

Server-side scripts

Stored procedures

user defined functions

JavaScript

yes

Triggers

JavaScript

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Partitioning is done manually, search queries against distributed index is supported

Sharding

Implicit feature of the cloud service

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

Synchronous replication based on Galera library

yes

Implicit feature of the cloud service

Journaling Streams

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session 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

yes

isolated transactions for atomic changes and binary logging for safe writes

Multi-item ACID transactions with snapshot isolation within a partition

ACID

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

yes

Durability

Support for making data persistent

yes

The original contents of fields are not stored in the Manticore index.

yes

in-memory journaling

User concepts

Access control

Access rights can be defined down to the item level

Role-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.