DBMS > BigObject vs. EsgynDB vs. OrigoDB vs. Splunk vs. TerarkDB

System Properties Comparison BigObject vs. EsgynDB vs. OrigoDB vs. Splunk vs. TerarkDB

Editorial information provided by DB-Engines

Name

Description

Analytic DBMS for real-time computations and queries

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

A fully ACID in-memory object graph database

Analytics Platform for Big Data

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

a hierachical model (tree) can be imposed

Relational DBMS

Document store
Object oriented DBMS

Search engine

Key-value store

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

Score	0.13
Rank	#333	Overall
	#147	Relational DBMS

Score	0.16
Rank	#329	Overall
	#146	Relational DBMS

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

Score	86.45
Rank	#14	Overall
	#2	Search engines

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

Website

github.com/bytedance/terarkdb

Technical documentation

docs.bigobject.io

origodb.com/docs

docs.splunk.com/Documentation/Splunk

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

Developer

BigObject, Inc.

Esgyn

Robert Friberg et al

Splunk Inc.

ByteDance, originally Terark

Initial release

2015

2009

under the name LiveDB

2003

2016

License

Commercial or Open Source

commercial

free community edition available

commercial

Open Source

commercial

Limited free edition and free developer edition available

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

distributed as a docker-image
OS X

distributed as a docker-image (boot2docker)
Windows

distributed as a docker-image (boot2docker)

Linux

Linux
Windows

Linux
OS X
Solaris
Windows

Data scheme

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.

can be achieved using .NET

yes

Secondary indexes

yes

SQL

Support of SQL

SQL-like DML and DDL statements

yes

Splunk Search Processing Language for search commands

APIs and other access methods

fluentd
ODBC
RESTful HTTP API

ADO.NET
JDBC
ODBC

.NET Client API
HTTP API
LINQ

HTTP REST

C++ API
Java API

Supported programming languages

All languages supporting JDBC/ODBC/ADO.Net

.Net

C#
Java
JavaScript
PHP
Python
Ruby

C++
Java

Server-side scripts

Stored procedures

Lua

Java Stored Procedures

yes

Triggers

yes

Domain Events

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

horizontal partitioning

client side managed; servers are not synchronized

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication between multi datacenters

Source-replica replication

Multi-source replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

automatically between fact table and dimension tables

yes

depending on model

Transaction concepts

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

ACID

A 'Transaction' in Splunk has a different meaning: grouping related events into a single one for later searching

Concurrency

Support for concurrent manipulation of data

yes

Read/write lock on objects (tables, trees)

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

Role based authorization

Access rights for users and roles

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

Enterprise Search Engines almost double their popularity in the last 12 months
2 July 2014, Paul Andlinger

show all

Share this page