DBMS > Alibaba Cloud Table Store vs. ClickHouse vs. Faircom EDGE vs. FatDB vs. Oracle Berkeley DB

System Properties Comparison Alibaba Cloud Table Store vs. ClickHouse vs. Faircom EDGE vs. FatDB vs. Oracle Berkeley DB

Editorial information provided by DB-Engines

Name

FatDB/FatCloud has ceased operations as a company with February 2014. FatDB is discontinued and excluded from the ranking.

Description

A fully managed Wide Column Store for large quantities of semi-structured data with real-time access

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.

FairCom EDGE is an Industry 4.0 solution built to integrate, collect, aggregate and synchronize mission-critical data in edge computing environments

A .NET NoSQL DBMS that can integrate with and extend SQL Server.

Widely used in-process key-value store

Primary database model

Wide column store

Relational DBMS

Key-value store
Relational DBMS

Document store
Key-value store

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Secondary database models

Time Series DBMS

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

Score	0.24
Rank	#310	Overall
	#12	Wide column stores

Score	16.20
Rank	#37	Overall
	#23	Relational DBMS

Score	0.03
Rank	#380	Overall
	#59	Key-value stores
	#157	Relational DBMS

Score	2.52
Rank	#114	Overall
	#20	Key-value stores
	#3	Native XML DBMS

Website

www.alibabacloud.com/product/table-store

clickhouse.com

www.faircom.com/products/faircom-edge

www.oracle.com/database/technologies/related/berkeleydb.html

Technical documentation

www.alibabacloud.com/help/en/tablestore

clickhouse.com/docs

docs.faircom.com/docs/en/UUID-23d4f1fd-d213-f6d5-b92e-9b7475baa14e.html

docs.oracle.com/cd/E17076_05/html/index.html

Developer

Alibaba

Clickhouse Inc.

FairCom Corporation

FatCloud

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Initial release

2016

1979

2012

1994

Current release

v23.12.1.1368-stable, December 2023

V3, October 2020

18.1.40, May 2020

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

commercial

Restricted, free version available

commercial

Open Source

commercial license 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.

Aiven for Clickhouse: Managed cloud data warehousing with high-speed analytics.
DoubleCloud: Fully managed ClickHouse alongside best-in-class managed open-source services to build analytics at scale.
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.

Implementation language

C++

ANSI C, C++

C, Java, C++ (depending on the Berkeley DB edition)

Server operating systems

hosted

FreeBSD
Linux
macOS

Android
Linux

ARM, x86
Raspbian
Windows

Windows

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Data scheme

schema-free

yes

Flexible Schema (defined schema, partial schema, schema free)

schema-free

Typing

predefined data types such as float or date

yes

yes, ANSI Standard SQL Types

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

only with the Berkeley DB XML edition

Secondary indexes

yes

SQL

Support of SQL

Close to ANSI SQL (SQL/JSON + extensions)

yes

ANSI SQL queries

Via inetgration in SQL Server

yes

SQL interfaced based on SQLite is available

APIs and other access methods

HTTP API

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

ADO.NET
Direct SQL
IoT Microservice layer
JDBC
MQTT (Message Queue Telemetry Transport)
ODBC
RESTful HTTP API

.NET Client API
LINQ
RESTful HTTP API
RPC
Windows WCF Bindings

Supported programming languages

Java
Python

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#
C++
Java
JavaScript
PHP
Python
VB.Net

.Net

Figaro is a .Net framework assembly that extends Berkeley DB XML into an embeddable database engine for .NET
others

Third-party libraries to manipulate Berkeley DB files are available for many languages
C
C#
C++
Java
JavaScript (Node.js)

3rd party binding
Perl
Python
Tcl

Server-side scripts

Stored procedures

yes

.Net, JavaScript, C/C++

yes

via applications

Triggers

yes

via applications

yes

only for the SQL API

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

key based and custom

File partitioning

Customizable business rules for partitioning

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Implicit feature of the cloud service

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

yes

Synchronous and asynchronous realtime replication based on transaction logs

selectable replication factor

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency
Tunable Consistency

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

when using SQL

Transaction concepts

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

Atomic single-row operations

ACID

Concurrency

Support for concurrent manipulation of data

yes

across SQL and NoSQL

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 based on subaccounts and tokens

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.

Fine grained user, group and file access rights managed across SQL (per ANSI standard) and NoSQL.

Can implement custom security layer via applications

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.