DBMS > Microsoft Access vs. Microsoft Azure Cosmos DB vs. Rockset vs. SiteWhere vs. SpaceTime

System Properties Comparison Microsoft Access vs. Microsoft Azure Cosmos DB vs. Rockset vs. SiteWhere vs. SpaceTime

Editorial information provided by DB-Engines

Name

Description

Microsoft Access combines a backend RDBMS (JET / ACE Engine) with a GUI frontend for data manipulation and queries.

The Access frontend is often used for accessing other datasources (DBMS, Excel, etc.)

Globally distributed, horizontally scalable, multi-model database service

A scalable, reliable search and analytics service in the cloud, built on RocksDB

M2M integration platform for persisting/querying time series data

SpaceTime is a spatio-temporal DBMS with a focus on performance.

Primary database model

Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Document store

Time Series DBMS

Spatial DBMS

Secondary database models

Spatial DBMS

Relational DBMS
Search engine

Relational DBMS

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

Score	104.92
Rank	#11	Overall
	#8	Relational DBMS

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

Score	0.79
Rank	#211	Overall
	#35	Document stores

Score	0.06
Rank	#356	Overall
	#35	Time Series DBMS

Score	0.00
Rank	#383	Overall
	#7	Spatial DBMS

Website

www.microsoft.com/en-us/microsoft-365/access

azure.microsoft.com/services/cosmos-db

rockset.com

github.com/sitewhere/sitewhere

www.mireo.com/spacetime

Technical documentation

developer.microsoft.com/en-us/access

learn.microsoft.com/azure/cosmos-db

docs.rockset.com

sitewhere1.sitewhere.io/index.html

Developer

Microsoft

Rockset

SiteWhere

Mireo

Initial release

1992

2014

2019

2010

2020

Current release

1902 (16.0.11328.20222), March 2019

License

Commercial or Open Source

commercial

Bundled with Microsoft Office

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

C++

Java

C++

Server operating systems

Windows

Not a real database server, but making use of DLLs

hosted

Linux
OS X
Windows

Linux

Data scheme

yes

schema-free

predefined scheme

yes

Typing

predefined data types such as float or date

yes

JSON types

dynamic typing

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.

ingestion from XML files supported

Secondary indexes

yes

All properties auto-indexed by default

all fields are automatically indexed

SQL

Support of SQL

yes

but not compliant to any SQL standard

SQL-like query language

Read-only SQL queries, including JOINs

A subset of ANSI SQL is implemented

APIs and other access methods

ADO.NET
DAO
ODBC
OLE DB

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

HTTP REST

RESTful HTTP API

Supported programming languages

C
C#
C++
Delphi
Java (JDBC-ODBC)
VBA
Visual Basic.NET

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

Go
Java
JavaScript (Node.js)
Python

C#
C++
Python

Server-side scripts

Stored procedures

yes

since Access 2010 using the ACE-engine

JavaScript

Triggers

yes

since Access 2010 using the ACE-engine

JavaScript

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Implicit feature of the cloud service

Automatic sharding

Sharding

based on HBase

Fixed-grid hypercubes

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

Implicit feature of the cloud service

yes

selectable replication factor

based on HBase

Real-time block device replication (DRBD)

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

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

but no files for transaction logging

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

but no files for transaction logging

yes

In-memory capabilities

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

User concepts

Access control

a simple user-level security was built in till version Access 2003

Access rights can be defined down to the item level

Access rights for users and organizations can be defined via Rockset console

Users with fine-grained authorization concept

yes

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.