DBMS > Amazon Neptune vs. BoltDB vs. Couchbase vs. EsgynDB vs. RDF4J

System Properties Comparison Amazon Neptune vs. BoltDB vs. Couchbase vs. EsgynDB vs. RDF4J

Editorial information provided by DB-Engines

Name

Description

Fast, reliable graph database built for the cloud

A distributed document store with integrated cache, a powerful search engine, in-built operational and analytical capabilities, and an embedded mobile database

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

RDF4J is a Java framework for processing RDF data, supporting both memory-based and a disk-based storage.

Primary database model

Secondary database models

Key-value store

originating from the former Membase product and supporting the Memcached protocol
Spatial DBMS

using the Geocouch extension
Search engine
Time Series DBMS
Vector DBMS

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

Score	2.20
Rank	#113	Overall
	#9	Graph DBMS
	#5	RDF stores

Score	0.70
Rank	#225	Overall
	#31	Key-value stores

Score	16.74
Rank	#33	Overall
	#5	Document stores

Score	0.15
Rank	#325	Overall
	#144	Relational DBMS

Score	0.72
Rank	#222	Overall
	#9	RDF stores

Website

aws.amazon.com/neptune

github.com/boltdb/bolt

www.couchbase.com

www.esgyn.cn

rdf4j.org

Technical documentation

aws.amazon.com/neptune/developer-resources

docs.couchbase.com

rdf4j.org/documentation

Developer

Amazon

Couchbase, Inc.

Esgyn

Since 2016 officially forked into an Eclipse project, former developer was Aduna Software.

Initial release

2017

2013

2011

2015

2004

Current release

Server: 7.2, June 2023; Mobile: 3.1, March 2022; Couchbase Capella (DBaaS), June 2023

License

Commercial or Open Source

commercial

Open Source

MIT License

Open Source

Business Source License (BSL 1.1); Commercial licenses also available

commercial

Open Source

Eclipse Distribution License (EDL), v1.0.

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, C++, Go and Erlang

C++, Java

Java

Server operating systems

hosted

BSD
Linux
OS X
Solaris
Windows

Linux
OS X
Windows

Linux

Linux
OS X
Unix
Windows

Data scheme

schema-free

yes

RDF Schemas

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.

Secondary indexes

yes

SQL

Support of SQL

SQL++, extends ANSI SQL to JSON for operational, transactional, and analytic use cases

yes

APIs and other access methods

OpenCypher
RDF 1.1 / SPARQL 1.1
TinkerPop Gremlin

CLI Client
HTTP REST
Kafka Connector
Native language bindings for CRUD, Query, Search and Analytics APIs
Spark Connector
Spring Data

ADO.NET
JDBC
ODBC

Java API
RIO

RDF Input/Output
Sail API
SeRQL

Sesame RDF Query Language
Sesame REST HTTP Protocol
SPARQL

Supported programming languages

C#
Go
Java
JavaScript
PHP
Python
Ruby
Scala

.Net
C
Go
Java
JavaScript

Node.js
Kotlin
PHP
Python
Ruby
Scala

All languages supporting JDBC/ODBC/ADO.Net

Java
PHP
Python

Server-side scripts

Stored procedures

Functions and timers in JavaScript and UDFs in Java, Python, SQL++

Java Stored Procedures

yes

Triggers

yes

via the TAP protocol

yes

Partitioning methods

Methods for storing different data on different nodes

none

Automatic Sharding

Sharding

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.

none

Multi-source replication

including cross data center replication
Source-replica replication

Multi-source replication between multi datacenters

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

Eventual Consistency
Immediate Consistency

selectable on a per-operation basis

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

yes

ACID

Isolation support depends on the API used

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

with encyption-at-rest

yes

in-memory storage is supported as well

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

Ephemeral buckets

User concepts

Access control

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

User and Administrator separation with password-based and LDAP integrated Authentication. Role-base 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.