DBMS > Amazon Neptune vs. etcd vs. OpenEdge vs. Oracle Berkeley DB vs. SQLite

System Properties Comparison Amazon Neptune vs. etcd vs. OpenEdge vs. Oracle Berkeley DB vs. SQLite

Editorial information provided by DB-Engines

Name

Description

Fast, reliable graph database built for the cloud

A distributed reliable key-value store

Application development environment with integrated database management system

Widely used in-process key-value store

Widely used embeddable, in-process RDBMS

Primary database model

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	2.20
Rank	#119	Overall
	#9	Graph DBMS
	#5	RDF stores

Score	7.25
Rank	#54	Overall
	#5	Key-value stores

Score	3.51
Rank	#86	Overall
	#46	Relational DBMS

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

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

aws.amazon.com/neptune

etcd.io
github.com/etcd-io/etcd

www.progress.com/openedge

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

www.sqlite.org

Technical documentation

aws.amazon.com/neptune/developer-resources

etcd.io/docs
github.com/etcd-io/etcd/tree/master/Documentation

documentation.progress.com/output/ua/OpenEdge_latest

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

www.sqlite.org/docs.html

Developer

Amazon

Progress Software Corporation

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Dwayne Richard Hipp

Initial release

2017

1984

1994

2000

Current release

3.4, August 2019

OpenEdge 12.2, March 2020

18.1.40, May 2020

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

commercial

Open Source

commercial license available

Open Source

Public Domain

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)

Server operating systems

hosted

FreeBSD
Linux
Windows

experimental

AIX
HP-UX
Linux
Solaris
Windows

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

server-less

Data scheme

schema-free

yes

schema-free

yes

dynamic column types

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

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

SQL-92 is not fully supported

APIs and other access methods

OpenCypher
RDF 1.1 / SPARQL 1.1
TinkerPop Gremlin

gRPC
JSON over HTTP

JDBC
ODBC

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

C#
Go
Java
JavaScript
PHP
Python
Ruby
Scala

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby
Rust
Scala
Tcl

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

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Server-side scripts

Stored procedures

yes

Triggers

yes, watching key changes

yes

only for the SQL API

yes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning

since Version 11.4

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-availability zones high availability, asynchronous replication for up to 15 read replicas within a single region. Global database clusters consists of a primary write DB cluster in one region, and up to five secondary read DB clusters in different regions. Each secondary region can have up to 16 reader instances.

Using Raft consensus algorithm to ensure data replication with strong consistency among multiple replicas.

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

Relationships in graphs

yes

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

Durability

Support for making data persistent

yes

with encyption-at-rest

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

Access rights for users and roles can be defined via the AWS Identity and Access Management (IAM)

Users and groups

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.