DBMS > Amazon Neptune vs. Atos Standard Common Repository vs. TerminusDB vs. Tkrzw

System Properties Comparison Amazon Neptune vs. Atos Standard Common Repository vs. TerminusDB vs. Tkrzw

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

This system has been discontinued and will be removed from the DB-Engines ranking.

Description

Fast, reliable graph database built for the cloud

Highly scalable database system, designed for managing session and subscriber data in modern mobile communication networks

Scalable Graph Database platform making enterprise data available by exploiting inferred entities and relationships

A concept of libraries, allowing an application program to store and query key-value pairs in a file. Successor of Tokyo Cabinet and Kyoto Cabinet

Primary database model

Graph DBMS
RDF store

Document store
Key-value store

Graph DBMS

Key-value store

Secondary database models

Document store
RDF store

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	0.23
Rank	#316	Overall
	#27	Graph DBMS

Score	0.07
Rank	#372	Overall
	#57	Key-value stores

Website

aws.amazon.com/neptune

atos.net/en/convergence-creators/portfolio/standard-common-repository

terminusdb.com

dbmx.net/tkrzw

Technical documentation

aws.amazon.com/neptune/developer-resources

terminusdb.github.io/terminusdb/#

Developer

Amazon

Atos Convergence Creators

DataChemist Ltd.

Mikio Hirabayashi

Initial release

2017

2016

2018

2020

Current release

1703

11.0.0, January 2023

0.9.3, August 2020

License

Commercial or Open Source

commercial

Open Source

GPL V3

Open Source

Apache Version 2.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

Java

Prolog, Rust

C++

Server operating systems

hosted

Linux

Linux
macOS

Data scheme

schema-free

Schema and schema-less with LDAP views

yes

schema-free

Typing

predefined data types such as float or date

yes

optional

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

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language (WOQL)

APIs and other access methods

OpenCypher
RDF 1.1 / SPARQL 1.1
TinkerPop Gremlin

LDAP

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

Supported programming languages

C#
Go
Java
JavaScript
PHP
Python
Ruby
Scala

All languages with LDAP bindings

JavaScript
Python

C++
Java
Python
Ruby

Server-side scripts

Stored procedures

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

cell division

Graph Partitioning

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.

yes

Journaling Streams

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

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

Atomic execution of specific operations

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

with encyption-at-rest

yes

in-memory journaling

yes

In-memory capabilities

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

yes

using specific database classes

User concepts

Access control

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

LDAP bind authentication

Role-based access control

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

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

Building NHM London's Planetary Knowledge Base with Amazon Neptune and the Registry of Open Data on AWS ...
5 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

Amazon Neptune Analytics is now available in the AWS Europe (London) Region
14 March 2024, AWS Blog

provided by Google News

How TerminusDB is commercializing its open source graph database
16 March 2021, VentureBeat

TerminusDB Takes on Data Collaboration with a git-Like Approach
1 December 2020, The New Stack

Trinity College spinout TerminusDB secures €3.6m in investment
15 March 2021, The Irish Times

[MCR2030-CAMS-ARISE-UNDRR Webinar] Preventing cascading failures of critical assets: Using the Open-Source ...
12 April 2022, United Nations Office for Disaster Risk Reduction

Irish start-ups received €28m from Enterprise Ireland in 2021
7 April 2022, SiliconRepublic.com

provided by Google News

Share this page