DBMS > EsgynDB vs. MarkLogic vs. OrigoDB vs. PostGIS vs. TerarkDB

System Properties Comparison EsgynDB vs. MarkLogic vs. OrigoDB vs. PostGIS vs. TerarkDB

Editorial information provided by DB-Engines

Name

Description

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

Operational and transactional Enterprise NoSQL database

A fully ACID in-memory object graph database

Spatial extension of PostgreSQL

A key-value store forked from RocksDB with advanced compression algorithms. It can be used standalone or as a storage engine for MySQL and MongoDB

Primary database model

Relational DBMS

Document store
Native XML DBMS
RDF store

as of version 7
Search engine

Document store
Object oriented DBMS

Spatial DBMS

Key-value store

Secondary database models

Relational DBMS

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

Score	0.15
Rank	#325	Overall
	#144	Relational DBMS

Score	4.15
Rank	#70	Overall
	#11	Document stores
	#1	Native XML DBMS
	#1	RDF stores
	#8	Search engines

Score	0.00
Rank	#385	Overall
	#54	Document stores
	#21	Object oriented DBMS

Score	20.16
Rank	#29	Overall
	#1	Spatial DBMS

Score	0.00
Rank	#385	Overall
	#61	Key-value stores

Website

www.esgyn.cn

www.progress.com/marklogic

origodb.com

postgis.net

github.com/bytedance/terarkdb

Technical documentation

www.progress.com/marklogic/documentation

origodb.com/docs

postgis.net/documentation

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

Developer

Esgyn

MarkLogic Corp.

Robert Friberg et al

ByteDance, originally Terark

Initial release

2015

2001

2009

under the name LiveDB

2005

2016

Current release

11.0, December 2022

3.4.2, February 2024

License

Commercial or Open Source

commercial

restricted free version is available

Open Source

GPL v2.0

commercial

restricted open source version available

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

C++, Java

C++

Server operating systems

Linux

Linux
OS X
Windows

Linux
Windows

Data scheme

yes

schema-free

Schema can be enforced

yes

schema-free

Typing

predefined data types such as float or date

yes

User defined using .NET types and collections

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

can be achieved using .NET

yes

Secondary indexes

yes

SQL

Support of SQL

yes

SQL92

yes

APIs and other access methods

ADO.NET
JDBC
ODBC

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

.NET Client API
HTTP API
LINQ

C++ API
Java API

Supported programming languages

All languages supporting JDBC/ODBC/ADO.Net

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

.Net

C++
Java

Server-side scripts

Stored procedures

Java Stored Procedures

yes

via XQuery or JavaScript

yes

user defined functions

Triggers

yes

Domain Events

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

client side managed; servers are not synchronized

yes

based on PostgreSQL

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication between multi datacenters

yes

Source-replica replication

yes

based on PostgreSQL

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

yes

depending on model

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

Durability

Support for making data persistent

yes

Write ahead log

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

fine grained access rights according to SQL-standard

Role-based access control at the document and subdocument levels

Role based authorization

yes

based on PostgreSQL

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

DB-Engines blog posts

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

Conferences, events and webinars

more DBMS events

Progress MarkLogic World
Washington DC, 23-25 September 2024

Recent citations in the news

Progress Software announces speaker lineup for MarkLogic World Tour US
18 September 2024, TipRanks

Progress Brings Industry Leaders Together to Share Insights on AI and Data at MarkLogic World Tour US 2024
18 September 2024, Progress Investor Relations

Progress Brings Industry Leaders Together to Share Insights on AI and Data at MarkLogic World Tour US 2024
18 September 2024, StockTitan

Progress Announces Powerful New Generative AI Capabilities in Latest Release of MarkLogic Server
5 September 2024, Yahoo Finance

Vantage Closes Wholesale Deal in Santa Clara
30 May 2024, Data Center Knowledge

provided by Google News

Share this page