DBMS > AgensGraph vs. Amazon DocumentDB vs. Machbase Neo vs. Microsoft Azure Cosmos DB vs. Yanza

System Properties Comparison AgensGraph vs. Amazon DocumentDB vs. Machbase Neo vs. Microsoft Azure Cosmos DB vs. Yanza

Editorial information provided by DB-Engines

Name

Yanza seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

Multi-model database supporting relational and graph data models and built upon PostgreSQL

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

TimeSeries DBMS for AIoT and BigData

Globally distributed, horizontally scalable, multi-model database service

Time Series DBMS for IoT Applications

Primary database model

Graph DBMS
Relational DBMS

Document store

Time Series DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Time Series DBMS

Secondary database models

Spatial DBMS

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

Score	0.20
Rank	#321	Overall
	#27	Graph DBMS
	#143	Relational DBMS

Score	1.91
Rank	#132	Overall
	#24	Document stores

Score	0.12
Rank	#339	Overall
	#30	Time Series DBMS

Score	29.04
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Website

bitnine.net/agensgraph

aws.amazon.com/documentdb

machbase.com

azure.microsoft.com/services/cosmos-db

yanza.com

Technical documentation

bitnine.net/documentation

aws.amazon.com/documentdb/resources

machbase.com/dbms

learn.microsoft.com/azure/cosmos-db

Developer

Bitnine Global Inc.

Machbase

Microsoft

Yanza

Initial release

2016

2019

2013

2014

2015

Current release

2.1, December 2018

V8.0, August 2023

License

Commercial or Open Source

Open Source

Apache License 2.0

commercial

free test version available

commercial

free version available

Cloud-based only

Only available as a cloud service

yes

but mainly used as a service provided by Yanza

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Server operating systems

Linux
OS X
Windows

hosted

Linux
macOS
Windows

hosted

Windows

Data scheme

depending on used data model

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

JSON types

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

All properties auto-indexed by default

SQL

Support of SQL

yes

SQL-like query language

APIs and other access methods

Cypher Query Language
JDBC

proprietary protocol using JSON (MongoDB compatible)

gRPC
HTTP REST
JDBC
MQTT (Message Queue Telemetry Transport)
ODBC

DocumentDB API
Graph API (Gremlin)
MongoDB API
RESTful HTTP API
Table API

HTTP API

Supported programming languages

C
Java
JavaScript
Python

Go
Java
JavaScript (Node.js)
PHP
Python

C
C#
C++
Go
Java
JavaScript
PHP

via ODBC
Python
R

via ODBC
Scala

.Net
C#
Java
JavaScript
JavaScript (Node.js)
MongoDB client drivers written for various programming languages
Python

any language that supports HTTP calls

Server-side scripts

Stored procedures

yes

JavaScript

Triggers

JavaScript

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

no, but can be realized using table inheritance

none

Sharding

Implicit feature of the cloud service

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

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

selectable replication factor

yes

Implicit feature of the cloud service

none

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

typically not used, however similar functionality with DBRef possible

Transaction concepts

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

ACID

Atomic single-document operations

Multi-item ACID transactions with snapshot isolation within a partition

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

In-memory capabilities

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

yes

volatile and lookup table

User concepts

Access control

fine grained access rights according to SQL-standard

Access rights for users and roles

simple password-based access control

Access rights can be defined down to the item level

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.