DBMS > BaseX vs. Microsoft Azure Cosmos DB vs. SwayDB vs. TigerGraph

System Properties Comparison BaseX vs. Microsoft Azure Cosmos DB vs. SwayDB vs. TigerGraph

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Light-weight Native XML DBMS with support for XQuery 3.0 and interactive GUI.

Globally distributed, horizontally scalable, multi-model database service

An embeddable, non-blocking, type-safe key-value store for single or multiple disks and in-memory storage

A complete, distributed, parallel graph computing platform supporting web-scale data analytics in real-time

Primary database model

Native XML DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Key-value store

Graph DBMS

Secondary database models

Spatial DBMS

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

Score	1.84
Rank	#135	Overall
	#4	Native XML DBMS

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

Score	0.04
Rank	#387	Overall
	#61	Key-value stores

Score	1.80
Rank	#138	Overall
	#13	Graph DBMS

Website

basex.org

azure.microsoft.com/services/cosmos-db

swaydb.simer.au

www.tigergraph.com

Technical documentation

docs.basex.org

learn.microsoft.com/azure/cosmos-db

docs.tigergraph.com

Developer

BaseX GmbH

Microsoft

Simer Plaha

Initial release

2007

2014

2018

2017

Current release

11.0, June 2024

License

Commercial or Open Source

Open Source

BSD license

commercial

Open Source

GNU Affero GPL V3.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

Scala

C++

Server operating systems

Linux
OS X
Windows

hosted

Linux

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

XQuery supports types

yes

JSON types

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

All properties auto-indexed by default

SQL

Support of SQL

SQL-like query language

SQL-like query language (GSQL)

APIs and other access methods

Java API
RESTful HTTP API
RESTXQ
WebDAV
XML:DB
XQJ

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

GSQL (TigerGraph Query Language)
Kafka
RESTful HTTP/JSON API

Supported programming languages

Actionscript
C
C#
Haskell
Java
JavaScript

Node.js
Lisp
Perl
PHP
Python
Qt
Rebol
Ruby
Scala
Visual Basic

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

Java
Kotlin
Scala

C++
Java

Server-side scripts

Stored procedures

yes

JavaScript

yes

Triggers

yes

via events

JavaScript

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Implicit feature of the cloud service

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

Implicit feature of the cloud service

none

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Relationships in graphs

Transaction concepts

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

multiple readers, single writer

Multi-item ACID transactions with snapshot isolation within a partition

Atomic execution of operations

ACID

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

User concepts

Access control

Users with fine-grained authorization concept on 4 levels

Access rights can be defined down to the item level

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.