DBMS > Apache Pinot vs. BoltDB vs. Microsoft Azure Data Explorer vs. RocksDB

System Properties Comparison Apache Pinot vs. BoltDB vs. Microsoft Azure Data Explorer vs. RocksDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Realtime distributed OLAP datastore, designed to answer OLAP queries with low latency

An embedded key-value store for Go.

Fully managed big data interactive analytics platform

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

Primary database model

column oriented

Secondary database models

Document store

If a column is of type dynamic docs.microsoft.com/en-us/azure/kusto/query/scalar-data-types/dynamic then it's possible to add arbitrary JSON documents in this cell
Event Store

this is the general usage pattern at Microsoft. Billing, Logs, Telemetry events are stored in ADX and the state of an individual entity is defined by the arg_max(timestamps)
Spatial DBMS
Search engine

support for complex search expressions docs.microsoft.com/en-us/azure/kusto/query/parseoperator FTS, Geospatial docs.microsoft.com/en-us/azure/kusto/query/geo-point-to-geohash-function distributed search -> ADX acts as a distributed search engine
Time Series DBMS

see docs.microsoft.com/en-us/azure/data-explorer/time-series-analysis

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

Score	0.38
Rank	#275	Overall
	#126	Relational DBMS

Score	0.80
Rank	#215	Overall
	#31	Key-value stores

Score	3.80
Rank	#81	Overall
	#43	Relational DBMS

Score	3.41
Rank	#86	Overall
	#11	Key-value stores

Website

pinot.apache.org

github.com/boltdb/bolt

azure.microsoft.com/services/data-explorer

rocksdb.org

Technical documentation

docs.pinot.apache.org

docs.microsoft.com/en-us/azure/data-explorer

github.com/facebook/rocksdb/wiki

Developer

Apache Software Foundation and contributors

Microsoft

Facebook, Inc.

Initial release

2015

2013

2019

2013

Current release

1.0.0, September 2023

cloud service with continuous releases

9.2.1, May 2024

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

MIT License

commercial

Open Source

BSD

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

Java

C++

Server operating systems

All OS with a Java JDK11 or higher

BSD
Linux
OS X
Solaris
Windows

hosted

Linux

Data scheme

yes

schema-free

Fixed schema with schema-less datatypes (dynamic)

schema-free

Typing

predefined data types such as float or date

yes

bool, datetime, dynamic, guid, int, long, real, string, timespan, double: docs.microsoft.com/en-us/azure/kusto/query/scalar-data-types

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

all fields are automatically indexed

SQL

Support of SQL

SQL-like query language

Kusto Query Language (KQL), SQL subset

APIs and other access methods

JDBC

Microsoft SQL Server communication protocol (MS-TDS)
RESTful HTTP API

C++ API
Java API

Supported programming languages

Go
Java
Python

.Net
Go
Java
JavaScript (Node.js)
PowerShell
Python
R

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

Yes, possible languages: KQL, Python, R

Triggers

yes

see docs.microsoft.com/en-us/azure/kusto/management/updatepolicy

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

none

Sharding

Implicit feature of the cloud service

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

Implicit feature of the cloud service. Replication either local, cross-facility or geo-redundant.

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Spark connector (open source): github.com/Azure/azure-kusto-spark

Consistency concepts

Methods to ensure consistency in a distributed system

none

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

Transaction concepts

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

yes

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

Azure Active Directory Authentication

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.