DBMS > Databricks vs. EXASOL vs. GridDB vs. InfinityDB vs. Snowflake

System Properties Comparison Databricks vs. EXASOL vs. GridDB vs. InfinityDB vs. Snowflake

Editorial information provided by DB-Engines

Name

Description

The Databricks Lakehouse Platform combines elements of data lakes and data warehouses to provide a unified view onto structured and unstructured data. It is based on Apache Spark.

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

Scalable in-memory time series database optimized for IoT and Big Data

A Java embedded Key-Value Store which extends the Java Map interface

Cloud-based data warehousing service for structured and semi-structured data

Primary database model

Document store
Relational DBMS

Secondary database models

Key-value store
Relational DBMS

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

Score	81.08
Rank	#15	Overall
	#2	Document stores
	#10	Relational DBMS

Score	1.76
Rank	#139	Overall
	#62	Relational DBMS

Score	2.09
Rank	#120	Overall
	#10	Time Series DBMS

Score	0.08
Rank	#365	Overall
	#55	Key-value stores

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

Technical documentation

docs.databricks.com

www.exasol.com/resources

docs.griddb.net

boilerbay.com/infinitydb/manual

docs.snowflake.net/manuals/index.html

Developer

Databricks

Exasol

Toshiba Corporation

Boiler Bay Inc.

Snowflake Computing Inc.

Initial release

2013

2000

2013

2002

2014

Current release

5.1, August 2022

4.0

License

Commercial or Open Source

commercial

Open Source

AGPL version 3 and Apache License, version 2.0 , commercial license (standard and advanced editions) also available

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

Java

Server operating systems

hosted

Linux

All OS with a Java VM

hosted

Data scheme

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

yes

nested virtual Java Maps, multi-value, logical â€˜tuple spaceâ€™ runtime Schema upgrade

yes

support of semi-structured data formats (JSON, XML, Avro)

Typing

predefined data types such as float or date

yes

numerical, string, blob, geometry, boolean, timestamp

yes

all Java primitives, Date, CLOB, BLOB, huge sparse arrays

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

manual creation possible, using inversions based on multi-value capability

SQL

Support of SQL

with Databricks SQL

yes

SQL92, SQL-like TQL (Toshiba Query Language)

yes

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

.Net
JDBC
ODBC
WebSocket

JDBC
ODBC
Proprietary protocol
RESTful HTTP/JSON API

Access via java.util.concurrent.ConcurrentNavigableMap Interface
Proprietary API to InfinityDB ItemSpace (boilerbay.com/docs/ItemSpaceDataStructures.htm)

CLI Client
JDBC
ODBC

Supported programming languages

Python
R
Scala

Java
Lua
Python
R

C
C++
Go
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

Java

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions and aggregates

user defined functions

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Hadoop integration

Connector for using GridDB as an input source and output destination for Hadoop MapReduce jobs

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate consistency within container, eventual consistency across containers

Immediate Consistency

READ-COMMITTED or SERIALIZED

Immediate Consistency

Foreign keys

Referential integrity

yes

manual creation possible, using inversions based on multi-value capability

yes

Transaction concepts

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

ACID

ACID at container level

ACID

Optimistic locking for transactions; no isolation for bulk loads

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, groups and roles according to SQL-standard

Access rights for users can be defined per database

Users with fine-grained authorization concept, user roles and pluggable authentication

More information provided by the system vendor

Specific characteristics

Supported database models : In addition to the Document store and Relational DBMS...
» more

GridDB is a highly scalable, in-memory time series database optimized for IoT and...
» more

Competitive advantages

1. Optimized for IoT Equipped with Toshiba's proprietary key-container data model...
» more

Typical application scenarios

Factory IoT, Automative Industry, Energy, BEMS, Smart Community, Monitoring system.
» more

Key customers

Denso International [see use case ] An Electric Power company [see use case ] Ishinomaki...
» more

Market metrics

GitHub trending repository
» more

Licensing and pricing models

Open Source license (AGPL v3 & Apache v2) Commercial license (subscription)
» more

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.