DBMS > BaseX vs. ClickHouse vs. Google Cloud Bigtable vs. JanusGraph vs. Microsoft Access

System Properties Comparison BaseX vs. ClickHouse vs. Google Cloud Bigtable vs. JanusGraph vs. Microsoft Access

Editorial information provided by DB-Engines

Name

Description

Light-weight Native XML DBMS with support for XQuery 3.0 and interactive GUI.

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.

Google's NoSQL Big Data database service. It's the same database that powers many core Google services, including Search, Analytics, Maps, and Gmail.

A Graph DBMS optimized for distributed clusters

It was forked from the latest code base of Titan in January 2017

Microsoft Access combines a backend RDBMS (JET / ACE Engine) with a GUI frontend for data manipulation and queries.

The Access frontend is often used for accessing other datasources (DBMS, Excel, etc.)

Primary database model

Native XML DBMS

Relational DBMS

Key-value store
Wide column store

Graph DBMS

Relational DBMS

Secondary database models

Time Series DBMS

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

Score	1.84
Rank	#135	Overall
	#4	Native XML DBMS

Score	15.55
Rank	#38	Overall
	#23	Relational DBMS

Score	3.15
Rank	#95	Overall
	#14	Key-value stores
	#8	Wide column stores

Score	2.02
Rank	#125	Overall
	#12	Graph DBMS

Score	101.16
Rank	#11	Overall
	#8	Relational DBMS

Website

basex.org

clickhouse.com

cloud.google.com/bigtable

janusgraph.org

www.microsoft.com/en-us/microsoft-365/access

Technical documentation

docs.basex.org

clickhouse.com/docs

cloud.google.com/bigtable/docs

docs.janusgraph.org

developer.microsoft.com/en-us/access

Developer

BaseX GmbH

Clickhouse Inc.

Google

Linux Foundation; originally developed as Titan by Aurelius

Microsoft

Initial release

2007

2016

2015

2017

1992

Current release

11.0, June 2024

v24.4.2.141-stable, June 2024

0.6.3, February 2023

1902 (16.0.11328.20222), March 2019

License

Commercial or Open Source

Open Source

BSD license

Open Source

Apache 2.0

commercial

Open Source

Apache 2.0

commercial

Bundled with Microsoft Office

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

Implementation language

Java

C++

Java

C++

Server operating systems

Linux
OS X
Windows

FreeBSD
Linux
macOS

hosted

Linux
OS X
Unix
Windows

Windows

Not a real database server, but making use of DLLs

Data scheme

schema-free

yes

schema-free

yes

Typing

predefined data types such as float or date

XQuery supports 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.

Secondary indexes

yes

SQL

Support of SQL

Close to ANSI SQL (SQL/JSON + extensions)

yes

but not compliant to any SQL standard

APIs and other access methods

Java API
RESTful HTTP API
RESTXQ
WebDAV
XML:DB
XQJ

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

gRPC (using protocol buffers) API
HappyBase (Python library)
HBase compatible API (Java)

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

ADO.NET
DAO
ODBC
OLE DB

Supported programming languages

Actionscript
C
C#
Haskell
Java
JavaScript

Node.js
Lisp
Perl
PHP
Python
Qt
Rebol
Ruby
Scala
Visual Basic

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)
Python

Clojure
Java
Python

C
C#
C++
Delphi
Java (JDBC-ODBC)
VBA
Visual Basic.NET

Server-side scripts

Stored procedures

yes

since Access 2010 using the ACE-engine

Triggers

yes

via events

yes

since Access 2010 using the ACE-engine

Partitioning methods

Methods for storing different data on different nodes

none

key based and custom

Sharding

yes

depending on the used storage backend (e.g. Cassandra, HBase, BerkeleyDB)

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

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

Internal replication in Colossus, and regional replication between two clusters in different zones

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via Faunus, a graph analytics engine

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate consistency (for a single cluster), Eventual consistency (for two or more replicated clusters)

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

Relationships in graphs

yes

Transaction concepts

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

multiple readers, single writer

Atomic single-row operations

ACID

but no files for transaction logging

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Supports various storage backends: Cassandra, HBase, Berkeley DB, Akiban, Hazelcast

yes

but no files for transaction logging

In-memory capabilities

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

yes

User concepts

Access control

Users with fine-grained authorization concept on 4 levels

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, groups and roles based on Google Cloud Identity and Access Management (IAM)

User authentification and security via Rexster Graph Server

a simple user-level security was built in till version Access 2003

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.