DBMS > Databricks vs. Firebird vs. OrientDB vs. SQLite

System Properties Comparison Databricks vs. Firebird vs. OrientDB vs. SQLite

Please select another system to include it in the comparison.

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.

Firebird is an open source RDBMS forked from Borland's InterBase

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

Widely used embeddable, in-process RDBMS

Primary database model

Document store
Relational DBMS

Relational DBMS

Document store
Graph DBMS
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	20.50
Rank	#30	Overall
	#18	Relational 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

Website

Technical documentation

docs.databricks.com

www.firebirdsql.org/en/reference-manuals

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

www.sqlite.org/docs.html

Developer

Databricks

Firebird Foundation

OrientDB LTD; CallidusCloud; SAP

Dwayne Richard Hipp

Initial release

2013

2000

As fork of Borland's InterBase

2010

2000

Current release

5.0.0, January 2024

3.2.29, March 2024

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

commercial

Open Source

Initial Developer's Public License

Open Source

Apache version 2

Open Source

Public Domain

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

Java

Server operating systems

hosted

AIX
FreeBSD
HP-UX
Linux
OS X
server-less

Firebird Embedded Server
Solaris
Unix
Windows

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

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

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

yes

SQL-like query language, no joins

yes

SQL-92 is not fully supported

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

ADO.NET
C/C++ API
JDBC

Jaybird
ODBC
OLE DB

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

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

Python
R
Scala

C
C#
C++
Delphi
Java
JavaScript

Node.js
Lua
Perl
PHP
Python
Ruby

.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

Server-side scripts

Stored procedures

user defined functions and aggregates

PSQL

Java, Javascript

Triggers

yes

Hooks

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

Multi-source replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

could be achieved with distributed queries

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

relationship in graphs

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Features a multi-generational MVCC architecture, readers do not block writers

yes

via file-system locks

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

Users with fine-grained authorization concept

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.