DBMS > Dolt vs. EXASOL vs. Google BigQuery vs. Splunk vs. Tarantool

System Properties Comparison Dolt vs. EXASOL vs. Google BigQuery vs. Splunk vs. Tarantool

Editorial information provided by DB-Engines

Name

Description

A MySQL compatible DBMS with Git-like versioning of data and schema

High-performance, in-memory, MPP database specifically designed for in-memory analytics.

Large scale data warehouse service with append-only tables

Analytics Platform for Big Data

In-memory computing platform with a flexible data schema for efficiently building high-performance applications

Primary database model

Relational DBMS

Search engine

Document store
Key-value store
Relational DBMS

Secondary database models

Document store

Spatial DBMS

with Tarantool/GIS extension

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

Score	1.02
Rank	#191	Overall
	#89	Relational DBMS

Score	1.76
Rank	#139	Overall
	#62	Relational DBMS

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	89.10
Rank	#14	Overall
	#2	Search engines

Score	1.67
Rank	#143	Overall
	#25	Document stores
	#25	Key-value stores
	#65	Relational DBMS

Website

github.com/dolthub/dolt
www.dolthub.com

www.exasol.com

cloud.google.com/bigquery

www.splunk.com

www.tarantool.io

Technical documentation

docs.dolthub.com

www.exasol.com/resources

cloud.google.com/bigquery/docs

docs.splunk.com/Documentation/Splunk

www.tarantool.io/en/doc

Developer

DoltHub Inc

Exasol

Google

Splunk Inc.

Initial release

2018

2000

2010

2003

2008

Current release

2.10.0, May 2022

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Limited free edition and free developer edition available

Open Source

BSD-2, source-available extensions (modules), commercial licenses for Tarantool Enterprise

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

C and C++

Server operating systems

Linux
macOS
Windows

hosted

Linux
OS X
Solaris
Windows

BSD
Linux
macOS

Data scheme

yes

Flexible data schema: relational definition for tables with ability to store json-like documents in columns

Typing

predefined data types such as float or date

yes

string, double, decimal, uuid, integer, blob, boolean, datetime

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

yes

Splunk Search Processing Language for search commands

Full-featured ANSI SQL support

APIs and other access methods

CLI Client
HTTP REST

.Net
JDBC
ODBC
WebSocket

RESTful HTTP/JSON API

HTTP REST

Open binary protocol

Supported programming languages

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Java
Lua
Python
R

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C#
Java
JavaScript
PHP
Python
Ruby

C
C#
C++
Erlang
Go
Java
JavaScript
Lua
Perl
PHP
Python
Rust

Server-side scripts

Stored procedures

yes

currently in alpha release

user defined functions

in JavaScript

yes

Lua, C and SQL stored procedures

Triggers

yes

yes, before/after data modification events, on replication events, client session events

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

Sharding

Sharding, partitioned with virtual buckets by user defined affinity key. Live resharding for scale up and scale down without maintenance downtime.

Replication methods

Methods for redundantly storing data on multiple nodes

A database can be cloned to multiple locations and be used there in isolation. Data/schema changes can be pushed/pulled explicitly between locations.

Multi-source replication

Asynchronous replication with multi-master option
Configurable replication topology (full-mesh, chain, star)
Synchronous quorum replication (with Raft)

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Hadoop integration

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Casual consistency across sharding partitions
Eventual consistency within replicaset partition

when using asyncronous replication
Immediate Consistency within single instance
Sequential consistency including linearizable read within replicaset partition

when using Raft

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Since BigQuery is designed for querying data

A 'Transaction' in Splunk has a different meaning: grouping related events into a single one for later searching

ACID, with serializable isolation and linearizable read (within partition); Configurable MVCC (within partition); No cross-shard distributed transactions

Concurrency

Support for concurrent manipulation of data

yes

yes, cooperative multitasking

Durability

Support for making data persistent

yes

yes, write ahead logging

In-memory capabilities

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

yes

yes, full featured in-memory storage engine with persistence

User concepts

Access control

Only one user is configurable, and must be specified in the config file at startup

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

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

Google Cloud Identity & Access Management (IAM)

Access rights for users and roles

Access Control Lists
Mutual TLS authentication for Tarantol Enterprise
Password based authentication
Role-based access control (RBAC) and LDAP for Tarantol Enterprise
Users and Roles

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.