DBMS > LeanXcale vs. OrigoDB vs. TerarkDB vs. Transwarp ArgoDB

System Properties Comparison LeanXcale vs. OrigoDB vs. TerarkDB vs. Transwarp ArgoDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A highly scalable full ACID SQL database with fast NoSQL data ingestion and GIS capabilities

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

Distributed Analytical Database to replace Hadoop+MPP hybrid architecture

Primary database model

Key-value store
Relational DBMS

Document store
Object oriented DBMS

Key-value store

Relational DBMS

Secondary database models

Search engine

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

Score	0.29
Rank	#291	Overall
	#41	Key-value stores
	#132	Relational DBMS

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

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

Score	0.07
Rank	#350	Overall
	#153	Relational DBMS

Website

www.leanxcale.com

origodb.com

github.com/bytedance/terarkdb

www.transwarp.cn/en/product/argodb

Technical documentation

origodb.com/docs

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

docs.transwarp.cn/#/documents-support/docs?category=ARGODB

Developer

LeanXcale

Robert Friberg et al

ByteDance, originally Terark

Transwarp

Initial release

2015

2009

under the name LiveDB

2016

License

Commercial or Open Source

commercial

Open Source

commercial

restricted open source version available

commercial

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++

Server operating systems

Linux
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

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

Secondary indexes

yes

SQL

Support of SQL

yes

through Apache Derby

yes

APIs and other access methods

JDBC
Kafka Connector
ODBC
proprietary key/value interface
Spark Connector

.NET Client API
HTTP API
LINQ

C++ API
Java API

Supported programming languages

C
Java
Scala

.Net

C++
Java

Server-side scripts

Stored procedures

yes

Triggers

yes

Domain Events

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

client side managed; servers are not synchronized

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

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

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.

Share this page