DBMS > Apache Kylin vs. Google BigQuery vs. Kingbase vs. RavenDB vs. TerarkDB

System Properties Comparison Apache Kylin vs. Google BigQuery vs. Kingbase vs. RavenDB vs. TerarkDB

Editorial information provided by DB-Engines

Name

Description

A distributed analytics engine for big data, providing a SQL interface and multi-dimensional analysis (OLAP) and leveraging the Hadoop stack

Large scale data warehouse service with append-only tables

An enterprise-class RDBMS compatible with PostgreSQL and Oracle and widely used in China.

Open Source Operational and Transactional Enterprise NoSQL Document 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

Document store

Key-value store

Secondary database models

Document store
Spatial DBMS

Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	1.18
Rank	#172	Overall
	#79	Relational DBMS

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	0.45
Rank	#262	Overall
	#123	Relational DBMS

Score	2.92
Rank	#101	Overall
	#18	Document stores

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

Website

kylin.apache.org

cloud.google.com/bigquery

www.kingbase.com.cn

ravendb.net

github.com/bytedance/terarkdb

Technical documentation

kylin.apache.org/docs

cloud.google.com/bigquery/docs

ravendb.net/docs

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

Developer

Apache Software Foundation, originally contributed from eBay Inc

Google

BeiJing KINGBASE Information technologies inc.

Hibernating Rhinos

ByteDance, originally Terark

Initial release

2015

2010

1999

2010

2016

Current release

3.1.0, July 2020

V8.0, August 2021

5.4, July 2022

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Open Source

AGPL version 3, commercial license 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 and Java

C++

Server operating systems

Linux

hosted

Linux
Windows

Linux
macOS
Raspberry Pi
Windows

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

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

ANSI SQL for queries (using Apache Calcite)

yes

Standard with numerous extensions

SQL-like query language (RQL)

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

RESTful HTTP/JSON API

ADO.NET
gokb
JDBC
kdbndp
ODBC
PDI
PDO
Pro*C
psycopg2
QT

.NET Client API
F# Client API
Go Client API
Java Client API
NodeJS Client API
PHP Client API
Python Client API
RESTful HTTP API

C++ API
Java API

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

.Net
C
C++
Go
Java
JavaScript (Node.js)
Perl
PHP
Python

.Net
C#
F#
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

C++
Java

Server-side scripts

Stored procedures

user defined functions

in JavaScript

user defined functions

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning (by range, list and hash) and vertical partitioning

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

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

Immediate Consistency

Default ACID transactions on the local node (eventually consistent across the cluster). Atomic operations with cluster-wide ACID transactions. Eventual consistency for indexes and full-text search indexes.

Foreign keys

Referential integrity

yes

Transaction concepts

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

Since BigQuery is designed for querying data

ACID

ACID, Cluster-wide transaction available

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

User concepts

Access control

Access privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

fine grained access rights according to SQL-standard

Authorization levels configured per client per database

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.