DBMS > Oracle Berkeley DB vs. Postgres-XL vs. SpatiaLite vs. Yanza

System Properties Comparison Oracle Berkeley DB vs. Postgres-XL vs. SpatiaLite vs. Yanza

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Yanza seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

Widely used in-process key-value store

Based on PostgreSQL enhanced with MPP and write-scale-out cluster features

Spatial extension of SQLite

Time Series DBMS for IoT Applications

Primary database model

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Relational DBMS

Spatial DBMS

Time Series DBMS

Secondary database models

Document store
Spatial DBMS

Relational DBMS

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

Score	2.21
Rank	#117	Overall
	#20	Key-value stores
	#3	Native XML DBMS

Score	0.49
Rank	#256	Overall
	#117	Relational DBMS

Score	1.60
Rank	#149	Overall
	#3	Spatial DBMS

Website

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

www.postgres-xl.org

www.gaia-gis.it/fossil/libspatialite/index

yanza.com

Technical documentation

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

www.postgres-xl.org/documentation

www.gaia-gis.it/gaia-sins/spatialite_topics.html

Developer

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Alessandro Furieri

Yanza

Initial release

1994

2014

since 2012, originally named StormDB

2008

2015

Current release

18.1.40, May 2020

10 R1, October 2018

5.0.0, August 2020

License

Commercial or Open Source

Open Source

commercial license available

Open Source

Mozilla public license

Open Source

MPL 1.1, GPL v2.0 or LGPL v2.1

commercial

free version available

Cloud-based only

Only available as a cloud service

but mainly used as a service provided by Yanza

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)

C++

Server operating systems

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Linux
macOS

server-less

Windows

Data scheme

schema-free

yes

schema-free

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

XML type, but no XML query functionality

Secondary indexes

yes

SQL

Support of SQL

yes

SQL interfaced based on SQLite is available

yes

distributed, parallel query execution

yes

APIs and other access methods

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

HTTP 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

.Net
C
C++
Delphi
Erlang
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

any language that supports HTTP calls

Server-side scripts

Stored procedures

user defined functions

Triggers

yes

only for the SQL API

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

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

MVCC

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

fine grained access rights according to SQL-standard

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

Recent citations in the news

Margo Seltzer Named ACM Athena Lecturer for Technical and Mentoring Contributions
26 April 2023, HPCwire

ACM recognizes far-reaching technical achievements with special awards
26 May 2021, EurekAlert

EC will investigate the Oracle/Sun takeover due to concerns about MySQL
3 September 2009, The Guardian

Database Trends Report: SQL Beats NoSQL, MySQL Most Popular -- ADTmag
5 March 2019, ADT Magazine

The importance of bitcoin nodes and how to start one
9 May 2014, The Merkle News

provided by Google News

Share this page