DBMS > EsgynDB vs. Infobright vs. OpenQM vs. OrigoDB vs. TerarkDB

System Properties Comparison EsgynDB vs. Infobright vs. OpenQM vs. OrigoDB vs. TerarkDB

Editorial information provided by DB-Engines

Name

Description

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

High performant column-oriented DBMS for analytic workloads using MySQL or PostgreSQL as a frontend

QpenQM is a high-performance, self-tuning, multi-value DBMS

A fully ACID in-memory object graph database

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

Multivalue DBMS

Document store
Object oriented DBMS

Key-value store

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

Score	0.16
Rank	#329	Overall
	#146	Relational DBMS

Score	0.96
Rank	#194	Overall
	#91	Relational DBMS

Score	0.27
Rank	#298	Overall
	#10	Multivalue DBMS

Score	0.00
Rank	#383	Overall
	#53	Document stores
	#20	Object oriented DBMS

Score	0.00
Rank	#383	Overall
	#60	Key-value stores

Website

www.esgyn.cn

ignitetech.com/softwarelibrary/infobrightdb

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-open-qm

origodb.com

github.com/bytedance/terarkdb

Technical documentation

origodb.com/docs

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

Developer

Esgyn

Ignite Technologies Inc.; formerly InfoBright Inc.

Rocket Software, originally Martin Phillips

Robert Friberg et al

ByteDance, originally Terark

Initial release

2015

2005

1993

2009

under the name LiveDB

2016

Current release

3.4-12

License

Commercial or Open Source

commercial

The open source (GPLv2) version did not support inserts/updates/deletes and was discontinued with July 2016

Open Source

GPLv2, extended commercial license available

Open Source

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
Windows

AIX
FreeBSD
Linux
macOS
Raspberry Pi
Solaris
Windows

Linux
Windows

Data scheme

yes

with some exceptions

yes

schema-free

Typing

predefined data types such as float or date

yes

User defined using .NET types and collections

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

Secondary indexes

yes

Knowledge Grid Technology used instead

yes

SQL

Support of SQL

yes

APIs and other access methods

ADO.NET
JDBC
ODBC

.NET Client API
HTTP API
LINQ

C++ API
Java API

Supported programming languages

All languages supporting JDBC/ODBC/ADO.Net

.Net
C
C#
C++
D
Eiffel
Erlang
Haskell
Java
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

.Net
Basic
C
Java
Objective C
PHP
Python

.Net

C++
Java

Server-side scripts

Stored procedures

Java Stored Procedures

yes

Triggers

yes

Domain Events

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

yes

horizontal partitioning

client side managed; servers are not synchronized

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication between multi datacenters

Source-replica replication

yes

Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

depending on model

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

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

User concepts

Access control

fine grained access rights according to SQL-standard

exploiting MySQL or PostgreSQL frontend capabilities

Access rights can be defined down to the item level

Role based authorization

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

Ignite Buys Database Vendor Infobright
2 May 2017, Datanami

provided by Google News

Share this page