DBMS > Apache Drill vs. BoltDB vs. Microsoft Azure Cosmos DB vs. Tibero

System Properties Comparison Apache Drill vs. BoltDB vs. Microsoft Azure Cosmos DB vs. Tibero

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Schema-free SQL Query Engine for Hadoop, NoSQL and Cloud Storage

An embedded key-value store for Go.

Globally distributed, horizontally scalable, multi-model database service

A secure RDBMS, designed for easy portability from Oracle

Primary database model

Document store
Relational DBMS

Key-value store

Document store
Graph DBMS
Key-value store
Wide column store

Relational DBMS

Secondary database models

Spatial DBMS

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

Score	1.95
Rank	#127	Overall
	#23	Document stores
	#60	Relational DBMS

Score	0.74
Rank	#220	Overall
	#31	Key-value stores

Score	29.04
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Score	1.78
Rank	#140	Overall
	#64	Relational DBMS

Website

drill.apache.org

github.com/boltdb/bolt

azure.microsoft.com/services/cosmos-db

us.tmaxsoft.com/products/tibero

Technical documentation

drill.apache.org/docs

learn.microsoft.com/azure/cosmos-db

technet.tmaxsoft.com/upload/download/online/tibero/pver-20150504-000002/index.html

Developer

Apache Software Foundation

Microsoft

TmaxSoft

Initial release

2012

2013

2014

2003

Current release

1.20.3, January 2023

6, April 2015

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

MIT License

commercial

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 Assembler

Server operating systems

Linux
OS X
Windows

BSD
Linux
OS X
Solaris
Windows

hosted

AIX
HP-UX
Linux
Solaris
Windows

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

JSON 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

Secondary indexes

yes

All properties auto-indexed by default

yes

SQL

Support of SQL

SQL SELECT statement is SQL:2003 compliant

SQL-like query language

yes

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

DocumentDB API
Graph API (Gremlin)
MongoDB API
RESTful HTTP API
Table API

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)
Tibero CLI

Supported programming languages

C++

.Net
C#
Java
JavaScript
JavaScript (Node.js)
MongoDB client drivers written for various programming languages
Python

C
C#
C++
Cobol
Java
Objective-C
Perl
PHP
Python
Ruby
Visual Basic

Server-side scripts

Stored procedures

user defined functions

JavaScript

Persistent Stored Procedure (PSM)

Triggers

JavaScript

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Implicit feature of the cloud service

horizontal partitioning

by range, hash, list or composite

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

Implicit feature of the cloud service

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

none

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

Multi-item ACID transactions with snapshot isolation within a partition

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

Depending on the underlying data source

yes

In-memory capabilities

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

Depending on the underlying data source

planned for next version

User concepts

Access control

Depending on the underlying data source

Access rights can be defined down to the item level

fine grained access rights according to SQL-standard (SQL 92, SQL 99)

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.