DBMS > Firebolt vs. Oracle Berkeley DB vs. RDF4J vs. Snowflake

System Properties Comparison Firebolt vs. Oracle Berkeley DB vs. RDF4J vs. Snowflake

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Highly scalable cloud data warehouse and analytics product

Forked from Clickhouse

Widely used in-process key-value store

RDF4J is a Java framework for processing RDF data, supporting both memory-based and a disk-based storage.

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

Primary database model

Relational DBMS

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

RDF store

Relational DBMS

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

Score	1.73
Rank	#140	Overall
	#63	Relational DBMS

Score	2.01
Rank	#126	Overall
	#21	Key-value stores
	#3	Native XML DBMS

Score	0.74
Rank	#222	Overall
	#9	RDF stores

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

www.firebolt.io

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

rdf4j.org

www.snowflake.com

Technical documentation

docs.firebolt.io

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

rdf4j.org/documentation

docs.snowflake.net/manuals/index.html

Developer

Firebolt Analytics Inc.

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Since 2016 officially forked into an Eclipse project, former developer was Aduna Software.

Snowflake Computing Inc.

Initial release

2020

1994

2004

2014

Current release

18.1.40, May 2020

License

Commercial or Open Source

commercial

Open Source

commercial license available

Open Source

Eclipse Distribution License (EDL), v1.0.

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)

Java

Server operating systems

hosted

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Linux
OS X
Unix
Windows

hosted

Data scheme

yes

schema-free

yes

RDF Schemas

yes

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

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

APIs and other access methods

.Net
ODBC
RESTful HTTP API

Java API
RIO

RDF Input/Output
Sail API
SeRQL

Sesame RDF Query Language
Sesame REST HTTP Protocol
SPARQL

CLI Client
JDBC
ODBC

Supported programming languages

Go
JavaScript (Node.js)
Python

.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

Java
PHP
Python

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

user defined functions

Triggers

yes

only for the SQL API

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

Source-replica replication

none

yes

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

Isolation support depends on the API used

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

in-memory storage is supported as well

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

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.