DBMS > BoltDB vs. ClickHouse vs. Teradata Aster vs. Valentina Server

System Properties Comparison BoltDB vs. ClickHouse vs. Teradata Aster vs. Valentina Server

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Teradata Aster has been integrated into other Teradata systems and therefore will be removed from the DB-Engines ranking.

Description

An embedded key-value store for Go.

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.

Platform for big data analytics on multistructured data sources and types

Object-relational database and reports server

Primary database model

Key-value store

Relational DBMS

Secondary database models

Time Series DBMS

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

Score	0.76
Rank	#224	Overall
	#32	Key-value stores

Score	16.20
Rank	#37	Overall
	#23	Relational DBMS

Score	0.18
Rank	#329	Overall
	#144	Relational DBMS

Website

github.com/boltdb/bolt

clickhouse.com

www.valentina-db.net

Technical documentation

clickhouse.com/docs

valentina-db.com/docs/dokuwiki/v5/doku.php

Developer

Clickhouse Inc.

Teradata

Paradigma Software

Initial release

2013

2016

2005

1999

Current release

v24.3.2.23-lts, April 2024

5.7.5

License

Commercial or Open Source

Open Source

MIT License

Open Source

Apache 2.0

commercial

Cloud-based only

Only available as a cloud service

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

Server operating systems

BSD
Linux
OS X
Solaris
Windows

FreeBSD
Linux
macOS

Linux

Linux
OS X
Windows

Data scheme

schema-free

yes

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

defined schema within the relational store; partial schema or schema free in the Aster File Store

yes

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

in Aster File Store

Secondary indexes

yes

SQL

Support of SQL

Close to ANSI SQL (SQL/JSON + extensions)

yes

APIs and other access methods

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

ADO.NET
JDBC
ODBC
OLE DB

ODBC

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#
C++
Java
Python
R

.Net
C
C#
C++
Objective-C
PHP
Ruby
Visual Basic
Visual Basic.NET

Server-side scripts

Stored procedures

yes

R packages

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

key based and custom

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

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

yes

Dimension tables are replicated across all nodes in the cluster. The number of replicas for the file store can be configured.

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

SQL Map-Reduce Framework

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

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.

fine grained access rights according to SQL-standard

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.