DBMS > Oracle Berkeley DB vs. Snowflake vs. Spark SQL vs. TerarkDB vs. TigerGraph

System Properties Comparison Oracle Berkeley DB vs. Snowflake vs. Spark SQL vs. TerarkDB vs. TigerGraph

Editorial information provided by DB-Engines

Name

Description

Widely used in-process key-value store

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

Spark SQL is a component on top of 'Spark Core' for structured data processing

A key-value store forked from RocksDB with advanced compression algorithms. It can be used standalone or as a storage engine for MySQL and MongoDB

A complete, distributed, parallel graph computing platform supporting web-scale data analytics in real-time

Primary database model

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Relational DBMS

Key-value store

Graph DBMS

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

Score	2.52
Rank	#114	Overall
	#20	Key-value stores
	#3	Native XML DBMS

Score	123.20
Rank	#9	Overall
	#6	Relational DBMS

Score	19.15
Rank	#33	Overall
	#20	Relational DBMS

Score	0.04
Rank	#377	Overall
	#58	Key-value stores

Score	1.83
Rank	#141	Overall
	#13	Graph DBMS

Website

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

www.snowflake.com

spark.apache.org/sql

github.com/bytedance/terarkdb

www.tigergraph.com

Technical documentation

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

docs.snowflake.net/manuals/index.html

spark.apache.org/docs/latest/sql-programming-guide.html

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

docs.tigergraph.com

Developer

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Snowflake Computing Inc.

Apache Software Foundation

ByteDance, originally Terark

Initial release

1994

2014

2016

2017

Current release

18.1.40, May 2020

3.5.0 ( 2.13), September 2023

License

Commercial or Open Source

Open Source

commercial license available

commercial

Open Source

Apache 2.0

commercial

restricted open source version 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, C++ (depending on the Berkeley DB edition)

Scala

C++

Server operating systems

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

hosted

Linux
OS X
Windows

Linux

Data scheme

schema-free

yes

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

yes

schema-free

yes

Typing

predefined data types such as float or date

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

only with the Berkeley DB XML edition

yes

Secondary indexes

yes

SQL

Support of SQL

yes

SQL interfaced based on SQLite is available

yes

SQL-like DML and DDL statements

SQL-like query language (GSQL)

APIs and other access methods

CLI Client
JDBC
ODBC

JDBC
ODBC

C++ API
Java API

GSQL (TigerGraph Query Language)
Kafka
RESTful HTTP/JSON API

Supported programming languages

.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

Java
Python
R
Scala

C++
Java

Server-side scripts

Stored procedures

user defined functions

yes

Triggers

yes

only for the SQL API

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

none

yes

yes, utilizing Spark Core

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

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

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

Role-based access control

More information provided by the system vendor

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.