DBMS > Databend vs. MaxDB vs. Oracle Berkeley DB vs. Snowflake

System Properties Comparison Databend vs. MaxDB vs. Oracle Berkeley DB vs. Snowflake

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

An open-source, elastic, and workload-aware cloud data warehouse designed to meet businesses' massive-scale analytics needs at low cost and with low complexity

A robust and reliable RDBMS optimized to run all major SAP solutions

Widely used in-process key-value store

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

Relational DBMS

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

Score	0.28
Rank	#287	Overall
	#131	Relational DBMS

Score	2.15
Rank	#115	Overall
	#55	Relational DBMS

Score	1.88
Rank	#130	Overall
	#23	Key-value stores
	#3	Native XML DBMS

Score	133.72
Rank	#7	Overall
	#5	Relational DBMS

Website

github.com/datafuselabs/databend
www.databend.com

maxdb.sap.com

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

www.snowflake.com

Technical documentation

docs.databend.com

maxdb.sap.com/documentation

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

docs.snowflake.net/manuals/index.html

Developer

Databend Labs

SAP, acquired from Software AG (Adabas-D) in 1997

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Snowflake Computing Inc.

Initial release

2021

1984

1994

2014

Current release

1.0.59, April 2023

7.9.10.12, February 2024

18.1.40, May 2020

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Limited community edition free

Open Source

commercial license 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

Rust

C++

C, Java, C++ (depending on the Berkeley DB edition)

Server operating systems

hosted
Linux
macOS

AIX
HP-UX
Linux
Solaris
Windows

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

hosted

Data scheme

yes

schema-free

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

CLI Client
JDBC
RESTful HTTP API

ADO.NET
JDBC
ODBC
WebDAV

CLI Client
JDBC
ODBC

Supported programming languages

Go
Java
JavaScript (Node.js)
Python
Rust

.Net
C#
Java
Perl
PHP
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

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

user defined functions

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

Replication methods

Methods for redundantly storing data on multiple nodes

none

Source-replica replication

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

yes

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

fine grained access rights according to SQL-standard

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.