DBMS > Amazon DocumentDB vs. JanusGraph vs. NSDb vs. searchxml

System Properties Comparison Amazon DocumentDB vs. JanusGraph vs. NSDb vs. searchxml

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Fast, scalable, highly available, and fully managed MongoDB-compatible database service

A Graph DBMS optimized for distributed clusters

It was forked from the latest code base of Titan in January 2017

Scalable, High-performance Time Series DBMS designed for Real-time Analytics on top of Kubernetes

DBMS for structured and unstructured content wrapped with an application server

Primary database model

Document store

Graph DBMS

Time Series DBMS

Native XML DBMS
Search engine

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

Score	1.91
Rank	#132	Overall
	#24	Document stores

Score	1.94
Rank	#129	Overall
	#12	Graph DBMS

Score	0.00
Rank	#383	Overall
	#41	Time Series DBMS

Score	0.00
Rank	#383	Overall
	#7	Native XML DBMS
	#25	Search engines

Website

aws.amazon.com/documentdb

janusgraph.org

nsdb.io

www.searchxml.net/category/products

Technical documentation

aws.amazon.com/documentdb/resources

docs.janusgraph.org

nsdb.io/Architecture

www.searchxml.net/support/handouts

Developer

Linux Foundation; originally developed as Titan by Aurelius

informationpartners gmbh

Initial release

2019

2017

2015

Current release

0.6.3, February 2023

1.0

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

Apache Version 2.0

commercial

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

Java, Scala

C++

Server operating systems

hosted

Linux
OS X
Unix
Windows

Linux
macOS

Windows

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

yes: int, bigint, decimal, string

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

all fields are automatically indexed

yes

SQL

Support of SQL

SQL-like query language

APIs and other access methods

proprietary protocol using JSON (MongoDB compatible)

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

gRPC
HTTP REST
WebSocket

RESTful HTTP API
WebDAV
XQuery
XSLT

Supported programming languages

Go
Java
JavaScript (Node.js)
PHP
Python

Clojure
Java
Python

Java
Scala

C++

most other programming languages supported via APIs

Server-side scripts

Stored procedures

yes

on the application server

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

yes

depending on the used storage backend (e.g. Cassandra, HBase, BerkeleyDB)

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-availability zones for high availability, asynchronous replication for up to 15 read replicas

yes

sychronisation to multiple collections

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

yes

via Faunus, a graph analytics engine

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

typically not used, however similar functionality with DBRef possible

yes

Relationships in graphs

Transaction concepts

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

Atomic single-document operations

ACID

multiple readers, single writer

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Supports various storage backends: Cassandra, HBase, Berkeley DB, Akiban, Hazelcast

Using Apache Lucene

yes

In-memory capabilities

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

User concepts

Access control

Access rights for users and roles

User authentification and security via Rexster Graph Server

Domain, group and role-based access control at the document level and for application services

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

Use LangChain and vector search on Amazon DocumentDB to build a generative AI chatbot | Amazon Web Services
20 May 2024, AWS Blog

Vector search for Amazon DocumentDB (with MongoDB compatibility) is now generally available | Amazon Web Services
29 November 2023, AWS Blog

AWS announces Amazon DocumentDB I/O-Optimized
21 November 2023, AWS Blog

AWS announces vector search for Amazon DocumentDB
29 November 2023, AWS Blog

Use headless clusters in Amazon DocumentDB for cost-effective multi-Region resiliency | Amazon Web Services
8 March 2024, AWS Blog

provided by Google News

JanusGraph Picks Up Where TitanDB Left Off
13 January 2017, Datanami

Database Deep Dives: JanusGraph
8 August 2019, ibm.com

From graph db to graph embedding. In 7 simple steps. | by Andy Greatorex
30 July 2020, Towards Data Science

Compose for JanusGraph arrives on Bluemix
15 September 2017, ibm.com

Nordstrom Builds Flexible Backend Ops with Kubernetes, Spark and JanusGraph
3 October 2019, The New Stack

provided by Google News

Share this page