DBMS > Databricks vs. Oracle Berkeley DB vs. Snowflake vs. SQLite

System Properties Comparison Databricks vs. Oracle Berkeley DB vs. Snowflake 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.

Widely used in-process key-value store

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

Widely used embeddable, in-process RDBMS

Primary database model

Document store
Relational DBMS

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

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	2.21
Rank	#117	Overall
	#20	Key-value stores
	#3	Native XML DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

www.databricks.com

www.oracle.com/database/technologies/related/berkeleydb.html

www.snowflake.com

www.sqlite.org

Technical documentation

docs.databricks.com

docs.oracle.com/cd/E17076_05/html/index.html

docs.snowflake.net/manuals/index.html

www.sqlite.org/docs.html

Developer

Databricks

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Snowflake Computing Inc.

Dwayne Richard Hipp

Initial release

2013

1994

2014

2000

Current release

18.1.40, May 2020

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

commercial

Open Source

commercial license available

commercial

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, Java, C++ (depending on the Berkeley DB edition)

Server operating systems

hosted

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

hosted

server-less

Data scheme

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

schema-free

yes

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

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

only with the Berkeley DB XML edition

yes

Secondary indexes

yes

SQL

Support of SQL

with Databricks SQL

yes

SQL interfaced based on SQLite is available

yes

SQL-92 is not fully supported

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

CLI Client
JDBC
ODBC

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

Python
R
Scala

.Net

Figaro is a .Net framework assembly that extends Berkeley DB XML into an embeddable database engine for .NET
others

Third-party libraries to manipulate Berkeley DB files are available for many languages
C
C#
C++
Java
JavaScript (Node.js)

3rd party binding
Perl
Python
Tcl

JavaScript (Node.js)
Python

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

user defined functions

Triggers

yes

only for the SQL API

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

none

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

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

Foreign keys

Referential integrity

yes

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

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

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.