DBMS > BaseX vs. Microsoft Azure Cosmos DB vs. SiteWhere vs. Snowflake

System Properties Comparison BaseX vs. Microsoft Azure Cosmos DB vs. SiteWhere vs. Snowflake

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

M2M integration platform for persisting/querying time series data

Cloud-based data warehousing service for structured and semi-structured data

Primary database model

Native XML DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Time Series DBMS

Relational 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.06
Rank	#383	Overall
	#43	Time Series DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

basex.org

azure.microsoft.com/services/cosmos-db

github.com/sitewhere/sitewhere

www.snowflake.com

Technical documentation

docs.basex.org

learn.microsoft.com/azure/cosmos-db

sitewhere1.sitewhere.io/index.html

docs.snowflake.net/manuals/index.html

Developer

BaseX GmbH

Microsoft

SiteWhere

Snowflake Computing Inc.

Initial release

2007

2014

2010

2014

Current release

10.7, August 2023

License

Commercial or Open Source

Open Source

BSD license

commercial

Open Source

Common Public Attribution License Version 1.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

Server operating systems

Linux
OS X
Windows

hosted

Linux
OS X
Windows

hosted

Data scheme

schema-free

predefined scheme

yes

support of semi-structured data formats (JSON, XML, Avro)

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.

yes

Secondary indexes

yes

All properties auto-indexed by default

SQL

Support of SQL

SQL-like query language

yes

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

HTTP REST

CLI Client
JDBC
ODBC

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

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

JavaScript

user defined functions

Triggers

yes

via events

JavaScript

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Implicit feature of the cloud service

Sharding

based on HBase

yes

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

Implicit feature of the cloud service

selectable replication factor

based on HBase

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

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

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

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.

User concepts

Access control

Users with fine-grained authorization concept on 4 levels

Access rights can be defined down to the item level

Users with fine-grained authorization concept

Users with fine-grained authorization concept, user roles and pluggable authentication

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.