DBMS > Amazon Redshift vs. Microsoft Azure Cosmos DB vs. SiteWhere vs. TimesTen

System Properties Comparison Amazon Redshift vs. Microsoft Azure Cosmos DB vs. SiteWhere vs. TimesTen

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

Globally distributed, horizontally scalable, multi-model database service

M2M integration platform for persisting/querying time series data

An in-memory SQL relational database that delivers microsecond response and high throughput for OLTP applications. TimesTen can be deployed as a standalone database or as a cache to a backend Oracle database.

Primary database model

Relational 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	15.25
Rank	#38	Overall
	#23	Relational DBMS

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

Score	0.07
Rank	#347	Overall
	#33	Time Series DBMS

Score	1.26
Rank	#164	Overall
	#75	Relational DBMS

Website

aws.amazon.com/redshift

azure.microsoft.com/services/cosmos-db

github.com/sitewhere/sitewhere

www.oracle.com/database/technologies/related/timesten.html

Technical documentation

docs.aws.amazon.com/redshift

learn.microsoft.com/azure/cosmos-db

sitewhere1.sitewhere.io/index.html

docs.oracle.com/en/database/other-databases/timesten/index.html

Developer

Amazon (based on PostgreSQL)

Microsoft

SiteWhere

Oracle

originally founded in HP Labs it was acquired by Oracle in 2005

Initial release

2012

2014

2010

1998

Current release

Release 22.1

License

Commercial or Open Source

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

hosted

Linux
OS X
Windows

IBM AIX Power PC 64-bit
Linux arm64
Linux x86-64
Solaris SPARC 64
Solaris SPARC/x86
Solaris x86-64

Data scheme

yes

schema-free

predefined scheme

yes

Typing

predefined data types such as float or date

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

restricted

yes

All properties auto-indexed by default

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

SQL-like query language

yes

APIs and other access methods

JDBC
ODBC

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

HTTP REST

ODBC
ODP.NET
Oracle Call Interface (OCI)
Pro*C/C++ programming interfaces
SQL and PL/SQL via JDBC

Supported programming languages

All languages supporting JDBC/ODBC

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

C
C++
Java
Node.js
PL/SQL
Python

Server-side scripts

Stored procedures

user defined functions

in Python

JavaScript

PL/SQL

Triggers

JavaScript

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

Sharding

based on HBase

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Implicit feature of the cloud service

selectable replication factor

based on HBase

Multi-source replication
Source-replica replication

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

Immediate Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

Transaction concepts

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

ACID

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

by means of logfiles and checkpoints

In-memory capabilities

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

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Access rights can be defined down to the item level

Users with fine-grained authorization concept

fine grained access rights according to SQL-standard

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.