DBMS > Amazon Neptune vs. Apache IoTDB vs. EJDB vs. EventStoreDB

System Properties Comparison Amazon Neptune vs. Apache IoTDB vs. EJDB vs. EventStoreDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Fast, reliable graph database built for the cloud

An IoT native database with high performance for data management and analysis, deployable on the edge and the cloud and integrated with Hadoop, Spark and Flink

Embeddable document-store database library with JSON representation of queries (in MongoDB style)

Industrial-strength, open-source database solution built from the ground up for event sourcing.

Primary database model

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

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

Score	1.31
Rank	#164	Overall
	#14	Time Series DBMS

Score	0.31
Rank	#296	Overall
	#44	Document stores

Score	1.19
Rank	#173	Overall
	#1	Event Stores

Website

aws.amazon.com/neptune

iotdb.apache.org

github.com/Softmotions/ejdb

www.eventstore.com

Technical documentation

aws.amazon.com/neptune/developer-resources

iotdb.apache.org/UserGuide/Master/QuickStart/QuickStart.html

github.com/Softmotions/ejdb/blob/master/README.md

developers.eventstore.com

Developer

Amazon

Apache Software Foundation

Softmotions

Event Store Limited

Initial release

2017

2018

2012

Current release

1.1.0, April 2023

21.2, February 2021

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

Open Source

GPLv2

Open Source

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

Java

Server operating systems

hosted

All OS with a Java VM (>= 1.8)

server-less

Linux
Windows

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

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-like query language

APIs and other access methods

OpenCypher
RDF 1.1 / SPARQL 1.1
TinkerPop Gremlin

JDBC
Native API

in-process shared library

Supported programming languages

C#
Go
Java
JavaScript
PHP
Python
Ruby
Scala

C
C#
C++
Go
Java
Python
Scala

Actionscript
C
C#
C++
Go
Java
JavaScript (Node.js)
Lua
Objective-C
Pike
Python
Ruby

Server-side scripts

Stored procedures

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning (by time range) + vertical partitioning (by deviceId)

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.

selectable replication methods; using Raft/IoTConsensus algorithm to ensure strong/eventual data consistency among multiple replicas

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Integration with Hadoop and Spark

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Strong Consistency with Raft

Foreign keys

Referential integrity

yes

Relationships in graphs

typically not needed, however similar functionality with collection joins possible

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

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)

yes

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

Recent citations in the news

Building NHM London's Planetary Knowledge Base with Amazon Neptune and the Registry of Open Data on AWS ...
5 June 2024, AWS Blog

Exploring new features of Apache TinkerPop 3.7.x in Amazon Neptune | Amazon Web Services
7 June 2024, AWS Blog

Unit testing Apache TinkerPop transactions: From TinkerGraph to Amazon Neptune | Amazon Web Services
3 June 2024, AWS Blog

AWS announces Amazon Neptune I/O-Optimized
22 February 2024, AWS Blog

AWS Weekly Roundup: LlamaIndex support for Amazon Neptune, force AWS CloudFormation stack deletion, and more ...
27 May 2024, AWS Blog

provided by Google News

AMD EPYC 4364P & 4564P @ DDR5-4800 / DDR5-5200 vs. Intel Xeon E-2488 Review
6 June 2024, Phoronix

TsFile: A Standard Format for IoT Time Series Data
27 February 2024, The New Stack

Linux 6.5 With AMD P-State EPP Default Brings Performance & Power Efficiency Benefits For Ryzen Servers
21 September 2023, Phoronix

Apache Promotes IoT Database Project
25 September 2020, Datanami

AMD EPYC 8324P / 8324PN Siena 32-Core Siena Linux Server Performance Review
10 October 2023, Phoronix

provided by Google News

Share this page