DBMS > OpenEdge vs. Oracle Berkeley DB vs. Oracle Rdb vs. RocksDB vs. SiteWhere

System Properties Comparison OpenEdge vs. Oracle Berkeley DB vs. Oracle Rdb vs. RocksDB vs. SiteWhere

Editorial information provided by DB-Engines

Name

Description

Application development environment with integrated database management system

Widely used in-process key-value store

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

M2M integration platform for persisting/querying time series 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

Key-value store

Time Series DBMS

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

Score	3.51
Rank	#86	Overall
	#46	Relational DBMS

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

Score	1.08
Rank	#184	Overall
	#85	Relational DBMS

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Score	0.06
Rank	#356	Overall
	#35	Time Series DBMS

Website

www.progress.com/openedge

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

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

rocksdb.org

github.com/sitewhere/sitewhere

Technical documentation

documentation.progress.com/output/ua/OpenEdge_latest

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

www.oracle.com/database/technologies/related/rdb-doc.html

github.com/facebook/rocksdb/wiki

sitewhere1.sitewhere.io/index.html

Developer

Progress Software Corporation

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Oracle, originally developed by Digital Equipment Corporation (DEC)

Facebook, Inc.

SiteWhere

Initial release

1984

1994

1984

2013

2010

Current release

OpenEdge 12.2, March 2020

18.1.40, May 2020

7.4.1.1, 2021

8.11.4, April 2024

License

Commercial or Open Source

commercial

Open Source

commercial license available

commercial

Open Source

BSD

Open Source

Common Public Attribution License Version 1.0

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.

Implementation language

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

C++

Java

Server operating systems

AIX
HP-UX
Linux
Solaris
Windows

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

HP Open VMS

Linux

Linux
OS X
Windows

Data scheme

yes

schema-free

Flexible Schema (defined schema, partial schema, schema free)

schema-free

predefined scheme

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

Secondary indexes

yes

SQL

Support of SQL

yes

close to SQL 92

yes

SQL interfaced based on SQLite is available

yes

APIs and other access methods

JDBC
ODBC

C++ API
Java API

HTTP REST

Supported programming languages

Progress proprietary ABL (Advanced Business Language)

.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

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

yes

Triggers

yes

only for the SQL API

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

since Version 11.4

none

horizontal partitioning

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

selectable replication factor

based on HBase

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

yes, on a single node

yes

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 and groups

Users with fine-grained authorization concept

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.