DBMS > Databricks vs. GeoMesa vs. OrientDB vs. SQLite vs. TinkerGraph

System Properties Comparison Databricks vs. GeoMesa vs. OrientDB vs. SQLite vs. TinkerGraph

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.

GeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.

Multi-model DBMS (Document, Graph, Key/Value)

Widely used embeddable, in-process RDBMS

A lightweight, in-memory graph engine that serves as a reference implementation of the TinkerPop3 API

Primary database model

Document store
Relational DBMS

Spatial DBMS

Document store
Graph DBMS
Key-value store

Relational DBMS

Graph 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	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	3.25
Rank	#89	Overall
	#16	Document stores
	#6	Graph DBMS
	#13	Key-value stores

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Score	0.13
Rank	#345	Overall
	#35	Graph DBMS

Website

tinkerpop.apache.org/docs/current/reference/#tinkergraph-gremlin

Technical documentation

docs.databricks.com

www.geomesa.org/documentation/stable/user/index.html

www.orientdb.com/docs/last/index.html

www.sqlite.org/docs.html

Developer

Databricks

CCRi and others

OrientDB LTD; CallidusCloud; SAP

Dwayne Richard Hipp

Initial release

2013

2014

2010

2000

2009

Current release

5.0.0, May 2024

3.2.29, March 2024

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

commercial

Open Source

Apache License 2.0

Open Source

Apache version 2

Open Source

Public Domain

Open Source

Apache 2.0

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

Scala

Java

Server operating systems

hosted

All OS with a Java JDK (>= JDK 6)

server-less

Data scheme

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

yes

schema-free

Schema can be enforced for whole record ("schema-full") or for some fields only ("schema-hybrid")

yes

dynamic column types

schema-free

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

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

SQL

Support of SQL

with Databricks SQL

SQL-like query language, no joins

yes

SQL-92 is not fully supported

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

Tinkerpop technology stack with Blueprints, Gremlin, Pipes
Java API
RESTful HTTP/JSON API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

TinkerPop 3

Supported programming languages

Python
R
Scala

.Net
C
C#
C++
Clojure
Java
JavaScript
JavaScript (Node.js)
PHP
Python
Ruby
Scala

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Groovy
Java

Server-side scripts

Stored procedures

user defined functions and aggregates

Java, Javascript

Triggers

Hooks

yes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

depending on storage layer

Multi-source replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

could be achieved with distributed queries

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

depending on storage layer

none

Foreign keys

Referential integrity

yes

relationship in graphs

yes

Relationships in graphs

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

Durability

Support for making data persistent

yes

optional

In-memory capabilities

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

depending on storage layer

yes

User concepts

Access control

yes

depending on the DBMS used for storage

Access rights for users and roles; record level security configurable

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.