DBMS > ClickHouse vs. GridDB vs. OceanBase vs. SAP SQL Anywhere vs. Yanza

System Properties Comparison ClickHouse vs. GridDB vs. OceanBase vs. SAP SQL Anywhere vs. Yanza

Editorial information provided by DB-Engines

Name

Yanza seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

A high-performance, column-oriented SQL DBMS for online analytical processing (OLAP) that uses all available system resources to their full potential to process each analytical query as fast as possible. It is available as both an open-source software and a cloud offering.

Scalable in-memory time series database optimized for IoT and Big Data

A distributed, high available RDBMS compatible with Oracle and MySQL

RDBMS database and synchronization technologies for server, desktop, remote office, and mobile environments

Time Series DBMS for IoT Applications

Primary database model

Secondary database models

Time Series DBMS

Key-value store
Relational DBMS

Document store
Wide column store

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

Score	16.34
Rank	#38	Overall
	#23	Relational DBMS

Score	1.95
Rank	#128	Overall
	#10	Time Series DBMS

Score	1.66
Rank	#147	Overall
	#68	Relational DBMS

Score	4.25
Rank	#79	Overall
	#43	Relational DBMS

Website

clickhouse.com

griddb.net

en.oceanbase.com

www.sap.com/products/technology-platform/sql-anywhere.html

yanza.com

Technical documentation

clickhouse.com/docs

docs.griddb.net

en.oceanbase.com/docs/oceanbase-database

help.sap.com/docs/SAP_SQL_Anywhere

Developer

Clickhouse Inc.

Toshiba Corporation

OceanBase

previously Alibaba and Ant Group

SAP

formerly Sybase

Yanza

Initial release

2016

2013

2010

1992

2015

Current release

v24.4.1.2088-stable, May 2024

5.1, August 2022

4.3.0, April 2024

17, July 2015

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

AGPL version 3 and Apache License, version 2.0 , commercial license (standard and advanced editions) also available

Open Source

Commercial license available

commercial

free version available

Cloud-based only

Only available as a cloud service

but mainly used as a service provided by Yanza

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

ClickHouse Cloud: Get the performance you love from open source ClickHouse in a serverless offering that takes care of the details so you can spend more time getting insight out of the fastest database on earth.
DoubleCloud: Fully managed ClickHouse alongside best-in-class managed open-source services to build analytics at scale.
Aiven for Clickhouse: Managed cloud data warehousing with high-speed analytics.

Implementation language

C++

Server operating systems

FreeBSD
Linux
macOS

Linux

AIX
HP-UX
Linux
OS X
Solaris
Windows

Windows

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

numerical, string, blob, geometry, boolean, timestamp

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

Close to ANSI SQL (SQL/JSON + extensions)

SQL92, SQL-like TQL (Toshiba Query Language)

yes

APIs and other access methods

gRPC
HTTP REST
JDBC
MySQL wire protocol
ODBC
PostgreSQL wire protocol
Proprietary protocol

JDBC
ODBC
Proprietary protocol
RESTful HTTP/JSON API

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)
Proprietary native API
Table API

ADO.NET
HTTP API
JDBC
ODBC

HTTP API

Supported programming languages

3rd party library
C++
Elixir

3rd party library
Go

3rd party library
Java

3rd party library
JavaScript (Node.js)

3rd party library
Kotlin

3rd party library
Nim

3rd party library
Perl

3rd party library
PHP

3rd party library
Python

3rd party library
R

3rd party library
Ruby

3rd party library
Rust
Scala

3rd party library

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

Ada

in MySQL-compatible model
C

in Oracle- and MySQL- compatible models
C++

in Oracle- and MySQL- compatible models
D

in MySQL-compatible model
Delphi

in MySQL-compatible model
Eiffel

in MySQL-compatible model
Erlang

in MySQL-compatible model
Haskell

in MySQL-compatible model
Java

in Oracle- and MySQL- compatible models
JavaScript (Node.js)

in MySQL-compatible model
Objective-C

in MySQL-compatible model
OCaml

in MySQL-compatible model
Perl

in MySQL-compatible model
PHP

in MySQL-compatible model
Python

in MySQL-compatible model
Ruby

in MySQL-compatible model
Scheme

in MySQL-compatible model
Tcl

in MySQL-compatible model

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

any language that supports HTTP calls

Server-side scripts

Stored procedures

yes

PL/SQL in oracle-compatible mode, MySQL Stored Procedure in mysql-compatible mode

yes, in C/C++, Java, .Net or Perl

Triggers

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

key based and custom

Sharding

horizontal partitioning (by hash, key, range, range columns, list, and list columns)

none

Replication methods

Methods for redundantly storing data on multiple nodes

Asynchronous and synchronous physical replication; geographically distributed replicas; support for object storages.

Source-replica replication

Multi-source replication using Paxos

Source-replica replication

Database mirroring

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Connector for using GridDB as an input source and output destination for Hadoop MapReduce jobs

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate consistency within container, eventual consistency across containers

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID at container level

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

User concepts

Access control

Access rights for users and roles. Column and row based policies. Quotas and resource limits. Pluggable authentication with LDAP and Kerberos. Password based, X.509 certificate, and SSH key authentication.

Access rights for users can be defined per database

Access rights for users, groups and roles according to SQL-standard

fine grained access rights according to SQL-standard

More information provided by the system vendor

Specific characteristics

GridDB is a highly scalable, in-memory time series database optimized for IoT and...
» more

OceanBase Database is the world’s only native distributed database that has set new...
» more

Competitive advantages

1. Optimized for IoT Equipped with Toshiba's proprietary key-container data model...
» more

High Availability : The five IDCs across three sites disaster recovery solution sets...
» more

Typical application scenarios

Factory IoT, Automative Industry, Energy, BEMS, Smart Community, Monitoring system.
» more

Key customers

Denso International [see use case ] An Electric Power company [see use case ] Ishinomaki...
» more

OceanBase Database has helped over 400 customers across industries upgrade their...
» more

Market metrics

GitHub trending repository
» more

TPC-C No.1 Performance , achieved a result of 707.35 million tpmC in the TPC-C benchmark...
» more

Licensing and pricing models

Open Source license (AGPL v3 & Apache v2) Commercial license (subscription)
» more

Mulan PubL v2 license for open source community edition. Commercial license for enterprise...
» more

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.