DBMS > atoti vs. Badger vs. OrigoDB vs. TerarkDB

System Properties Comparison atoti vs. Badger vs. OrigoDB vs. TerarkDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

An in-memory DBMS combining transactional and analytical processing to handle the aggregation of ever-changing data.

An embeddable, persistent, simple and fast Key-Value Store, written purely in Go.

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

Object oriented DBMS

Key-value store

Document store
Object oriented DBMS

Key-value store

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

Score	0.56
Rank	#245	Overall
	#10	Object oriented DBMS

Score	0.14
Rank	#331	Overall
	#49	Key-value stores

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

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

Website

atoti.io

github.com/dgraph-io/badger

origodb.com

github.com/bytedance/terarkdb

Technical documentation

docs.atoti.io

godoc.org/github.com/dgraph-io/badger

origodb.com/docs

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

Developer

ActiveViam

DGraph Labs

Robert Friberg et al

ByteDance, originally Terark

Initial release

2017

2009

under the name LiveDB

2016

License

Commercial or Open Source

commercial

free versions available

Open Source

Apache 2.0

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

Java

C++

Server operating systems

BSD
Linux
OS X
Solaris
Windows

Linux
Windows

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

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.

can be achieved using .NET

Secondary indexes

yes

SQL

Support of SQL

Multidimensional Expressions (MDX)

APIs and other access methods

.NET Client API
HTTP API
LINQ

C++ API
Java API

Supported programming languages

.Net

C++
Java

Server-side scripts

Stored procedures

Python

yes

Triggers

yes

Domain Events

Partitioning methods

Methods for storing different data on different nodes

Sharding, horizontal partitioning

none

horizontal partitioning

client side managed; servers are not synchronized

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

none

Foreign keys

Referential integrity

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, multi-version concurrency control (MVCC)

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

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

FRTB product of the year: ActiveViam
28 November 2023, Risk.net

provided by Google News

Share this page