DBMS > Oracle Berkeley DB vs. PostgreSQL vs. XTDB

System Properties Comparison Oracle Berkeley DB vs. PostgreSQL vs. XTDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Widely used in-process key-value store

Widely used open source RDBMS

Developed as objectoriented DBMS (Postgres), gradually enhanced with 'standards' like SQL

A general purpose database with bitemporal SQL and Datalog and graph queries

Primary database model

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Relational DBMS

with object oriented extensions, e.g.: user defined types/functions and inheritance. Handling of key/value pairs with hstore module.

Document store

Secondary database models

Document store
Graph DBMS

with Apache Age
Spatial DBMS
Vector DBMS

with pgvector extension

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

Score	1.72
Rank	#131	Overall
	#21	Key-value stores
	#3	Native XML DBMS

Score	674.32
Rank	#4	Overall
	#4	Relational DBMS

Score	0.20
Rank	#314	Overall
	#46	Document stores

Website

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

www.postgresql.org

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

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

www.postgresql.org/docs

www.xtdb.com/docs

Developer

Oracle

originally developed by Sleepycat, which was acquired by Oracle

PostgreSQL Global Development Group

www.postgresql.org/developer

Juxt Ltd.

Initial release

1994

1989

1989: Postgres, 1996: PostgreSQL

2019

Current release

18.1.40, May 2020

16.4, August 2024

1.19, September 2021

License

Commercial or Open Source

Open Source

commercial license available

Open Source

BSD

Open Source

MIT License

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

PostgreSQL Flex @ STACKIT offers managed PostgreSQL Instances with adjustable CPU, RAM, storage amount and speed and several extensions available, in enterprise grade to perfectly match all application requirements. All 100% GDPR-compliant.

Implementation language

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

Clojure

Server operating systems

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

FreeBSD
HP-UX
Linux
NetBSD
OpenBSD
OS X
Solaris
Unix
Windows

All OS with a Java 8 (and higher) VM
Linux

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

yes, extensible-data-notation format

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

specific XML-type available, but no XML query functionality.

Secondary indexes

yes

SQL

Support of SQL

yes

SQL interfaced based on SQLite is available

yes

standard with numerous extensions

limited SQL, making use of Apache Calcite

APIs and other access methods

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

HTTP REST
JDBC

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
Java

JDBC
JavaScript (Node.js)
Perl
PHP
Python
Tcl

Clojure
Java

Server-side scripts

Stored procedures

user defined functions

realized in proprietary language PL/pgSQL or with common languages like Perl, Python, Tcl etc.

Triggers

yes

only for the SQL API

yes

Partitioning methods

Methods for storing different data on different nodes

none

partitioning by range, list and (since PostgreSQL 11) by hash

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

other methods possible by using 3rd party extensions

yes, each node contains all data

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

Durability

Support for making data persistent

yes

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

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.