DBMS > HBase vs. MarkLogic vs. Snowflake vs. TerarkDB

System Properties Comparison HBase vs. MarkLogic vs. Snowflake vs. TerarkDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Wide-column store based on Apache Hadoop and on concepts of BigTable

Operational and transactional Enterprise NoSQL database

Cloud-based data warehousing service for structured and semi-structured 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

Wide column store

Document store
Native XML DBMS
RDF store

as of version 7
Search engine

Relational DBMS

Key-value store

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

Score	30.50
Rank	#26	Overall
	#2	Wide column stores

Score	5.92
Rank	#58	Overall
	#10	Document stores
	#1	Native XML DBMS
	#1	RDF stores
	#6	Search engines

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

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

Website

hbase.apache.org

www.marklogic.com

www.snowflake.com

github.com/bytedance/terarkdb

Technical documentation

hbase.apache.org/book.html

docs.marklogic.com

docs.snowflake.net/manuals/index.html

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

Developer

Apache Software Foundation

Apache top-level project, originally developed by Powerset

MarkLogic Corp.

Snowflake Computing Inc.

ByteDance, originally Terark

Initial release

2008

2001

2014

2016

Current release

2.3.4, January 2021

11.0, December 2022

License

Commercial or Open Source

Open Source

Apache version 2

commercial

restricted free version is available

commercial

restricted open source version available

Cloud-based only

Only available as a cloud service

yes

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

Linux
Unix
Windows

using Cygwin

Linux
OS X
Windows

hosted

Data scheme

schema-free, schema definition possible

schema-free

Schema can be enforced

yes

support of semi-structured data formats (JSON, XML, Avro)

schema-free

Typing

predefined data types such as float or date

options to bring your own types, AVRO

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

Secondary indexes

yes

SQL

Support of SQL

yes

SQL92

yes

APIs and other access methods

Java API
RESTful HTTP API
Thrift

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

CLI Client
JDBC
ODBC

C++ API
Java API

Supported programming languages

C
C#
C++
Groovy
Java
PHP
Python
Scala

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

JavaScript (Node.js)
Python

C++
Java

Server-side scripts

Stored procedures

yes

Coprocessors in Java

yes

via XQuery or JavaScript

user defined functions

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

yes

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 or Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

Single row ACID (across millions of columns)

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

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

yes, with Range Indexes

yes

User concepts

Access control

Access Control Lists (ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC

Role-based access control at the document and subdocument levels

Users with fine-grained authorization concept, user roles and pluggable authentication

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.