DBMS > Databricks vs. Kinetica vs. MySQL vs. Rockset vs. SpatiaLite

System Properties Comparison Databricks vs. Kinetica vs. MySQL vs. Rockset vs. SpatiaLite

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.

Fully vectorized database across both GPUs and CPUs

Widely used open source RDBMS

A scalable, reliable search and analytics service in the cloud, built on RocksDB

Spatial extension of SQLite

Primary database model

Document store
Relational DBMS

Relational DBMS

Key/Value like access via memcached API

Document store

Spatial DBMS

Secondary database models

Spatial DBMS
Time Series DBMS

Document store
Spatial DBMS

Relational DBMS
Search engine

Relational DBMS

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

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

Score	0.64
Rank	#236	Overall
	#109	Relational DBMS

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	0.79
Rank	#211	Overall
	#35	Document stores

Score	1.60
Rank	#149	Overall
	#3	Spatial DBMS

Website

www.gaia-gis.it/fossil/libspatialite/index

Technical documentation

www.gaia-gis.it/gaia-sins/spatialite_topics.html

Developer

Databricks

Kinetica

Oracle

since 2010, originally MySQL AB, then Sun

Rockset

Alessandro Furieri

Initial release

2013

2012

1995

2019

2008

Current release

7.1, August 2021

8.4.0, April 2024

5.0.0, August 2020

License

Commercial or Open Source

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

commercial

Open Source

MPL 1.1, GPL v2.0 or LGPL v2.1

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.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

C, C++

C and C++

C++

Server operating systems

hosted

Linux

FreeBSD
Linux
OS X
Solaris
Windows

hosted

server-less

Data scheme

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

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

dynamic typing

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

ingestion from XML files supported

Secondary indexes

yes

all fields are automatically indexed

yes

SQL

Support of SQL

with Databricks SQL

SQL-like DML and DDL statements

yes

with proprietary extensions

Read-only SQL queries, including JOINs

yes

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

ADO.NET
JDBC
ODBC
Proprietary native API

HTTP REST

Supported programming languages

Python
R
Scala

C++
Java
JavaScript (Node.js)
Python

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

Go
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions and aggregates

user defined functions

yes

proprietary syntax

Triggers

yes

triggers when inserted values for one or more columns fall within a specified range

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Automatic sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

Multi-source replication
Source-replica replication

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

Transaction concepts

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

ACID

not for MyISAM storage engine

ACID

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

GPU vRAM or System RAM

yes

User concepts

Access control

Access rights for users and roles on table level

Users with fine-grained authorization concept

no user groups or roles

Access rights for users and organizations can be defined via Rockset console

More information provided by the system vendor

Specific characteristics

Supported database models : In addition to the Document store and Relational DBMS...
» 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.