DBMS > Amazon DynamoDB vs. Faircom DB vs. GraphDB vs. Heroic vs. Oracle Berkeley DB

System Properties Comparison Amazon DynamoDB vs. Faircom DB vs. GraphDB vs. Heroic vs. Oracle Berkeley DB

Editorial information provided by DB-Engines

Name

Description

Hosted, scalable database service by Amazon with the data stored in Amazons cloud

Native high-speed multi-model DBMS for relational and key-value store data simultaneously accessible through SQL and NoSQL APIs.

Enterprise-ready RDF and graph database with efficient reasoning, cluster and external index synchronization support. It supports also SQL JDBC access to Knowledge Graph and GraphQL over SPARQL.

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

Widely used in-process key-value store

Primary database model

Document store
Key-value store

Key-value store
Relational DBMS

Graph DBMS
RDF store

Time Series DBMS

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

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

Score	74.07
Rank	#17	Overall
	#3	Document stores
	#2	Key-value stores

Score	0.20
Rank	#318	Overall
	#48	Key-value stores
	#141	Relational DBMS

Score	3.32
Rank	#91	Overall
	#6	Graph DBMS
	#4	RDF stores

Score	0.51
Rank	#255	Overall
	#21	Time Series DBMS

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

Website

aws.amazon.com/dynamodb

www.faircom.com/products/faircom-db

www.ontotext.com

github.com/spotify/heroic

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

Technical documentation

docs.aws.amazon.com/dynamodb

docs.faircom.com/docs/en/UUID-7446ae34-a1a7-c843-c894-d5322e395184.html

graphdb.ontotext.com/documentation

spotify.github.io/heroic

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

Social network pages

Developer

Amazon

FairCom Corporation

Ontotext

Spotify

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Initial release

2012

1979

2000

2014

1994

Current release

V12, November 2020

10.4, October 2023

18.1.40, May 2020

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

commercial

Restricted, free version available

commercial

Some plugins of GraphDB Workbench are open sourced

Open Source

Apache 2.0

Open Source

commercial license available

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

ANSI C, C++

Java

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

Server operating systems

hosted

AIX
FreeBSD
HP-UX
Linux
NetBSD
OS X
QNX
SCO
Solaris
VxWorks
Windows

easily portable to other OSs

All OS with a Java VM
Linux
OS X
Windows

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Data scheme

schema-free

schema free, schema optional, schema required, partial schema,

schema-free and OWL/RDFS-schema support; RDF shapes

schema-free

Typing

predefined data types such as float or date

yes

yes, ANSI SQL Types, JSON, typed binary structures

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

yes, supports real-time synchronization and indexing in SOLR/Elastic search/Lucene and GeoSPARQL geometry data indexes

yes

via Elasticsearch

yes

SQL

Support of SQL

yes, ANSI SQL with proprietary extensions

stored SPARQL accessed as SQL using Apache Calcite through JDBC/ODBC

yes

SQL interfaced based on SQLite is available

APIs and other access methods

RESTful HTTP API

ADO.NET
Direct SQL
JDBC
JPA
ODBC
RESTful HTTP/JSON API
RESTful MQTT/JSON API
RPC

GeoSPARQL
GraphQL
GraphQL Federation
Java API
JDBC
RDF4J API
RDFS
RIO
Sail API
Sesame REST HTTP Protocol
SPARQL 1.1

HQL (Heroic Query Language, a JSON-based language)
HTTP API

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

.Net
C
C#
C++
Java
JavaScript (Node.js and browser)
PHP
Python
Visual Basic

.Net
C#
Clojure
Java
JavaScript (Node.js)
PHP
Python
Ruby
Scala

.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

Server-side scripts

Stored procedures

yes

.Net, JavaScript, C/C++

well-defined plugin interfaces; JavaScript server-side extensibility

Triggers

yes

by integration with AWS Lambda

yes

only for the SQL API

Partitioning methods

Methods for storing different data on different nodes

Sharding

File partitioning, horizontal partitioning, sharding

Customizable business rules for table partitioning

none

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

yes, configurable to be parallel or serial, synchronous or asynchronous, uni-directional or bi-directional, ACID-consistent or eventually consistent (with custom conflict resolution).

Multi-source replication

yes

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

can be specified for read operations

Eventual Consistency
Immediate Consistency
Tunable consistency per server, database, table, and transaction

Immediate Consistency, Eventual consistency (configurable in cluster mode per master or individual client request)

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

Constraint checking

Transaction concepts

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

ACID

ACID across one or more tables within a single AWS account and region

tunable from ACID to Eventually Consistent

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Yes, tunable from durable to delayed durability to in-memory

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)

Fine grained access rights according to SQL-standard with additional protections for files

Default Basic authentication through RDF4J client, or via Java when run with cURL, default token-based in the Workbench or via Rest API, optional access through OpenID or Kerberos single sign-on.

More information provided by the system vendor

Specific characteristics

Ontotext GraphDB is a semantic database engine that allows organizations to build...
» more

Competitive advantages

GraphDB allows you to link text and data in big knowledge graphs. It’s easy to experiment...
» more

Typical application scenarios

Metadata enrichment and management, linked data publishing, semantic inferencing...
» more

Key customers

GraphDB provides a platform for building next-generation AI and Knowledge Graph...
» more

Market metrics

GraphDB is the most utilized semantic triplestore for mission-critical enterprise...
» more

Licensing and pricing models

GraphDB Free is a non-commercial version and is free to use. GraphDB Enterprise edition...
» more

News

Understanding the Graph Center of Excellence
17 May 2024

Migrating From LPG to RDF Graph Model
8 May 2024

Case study: Policy Enforcement Automation With Semantics
2 May 2024

Okay, RAG… We Have a Problem
26 April 2024

Scaling Understanding with the Help of Feedback Loops, Knowledge Graphs and NLP
19 April 2024

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.