DBMS > Amazon Redshift vs. Microsoft Azure AI Search vs. Microsoft Azure Synapse Analytics vs. PlanetScale vs. SiteWhere

System Properties Comparison Amazon Redshift vs. Microsoft Azure AI Search vs. Microsoft Azure Synapse Analytics vs. PlanetScale vs. SiteWhere

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

Search-as-a-service for web and mobile app development

Elastic, large scale data warehouse service leveraging the broad eco-system of SQL Server

Scalable, distributed, serverless MySQL database platform built on top of Vitess

M2M integration platform for persisting/querying time series data

Primary database model

Secondary database models

Vector DBMS

Document store
Spatial DBMS

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	5.52
Rank	#59	Overall
	#6	Search engines

Score	19.93
Rank	#31	Overall
	#19	Relational DBMS

Score	1.49
Rank	#155	Overall
	#72	Relational DBMS

Score	0.06
Rank	#383	Overall
	#43	Time Series DBMS

Website

aws.amazon.com/redshift

azure.microsoft.com/en-us/services/search

azure.microsoft.com/services/synapse-analytics

planetscale.com

github.com/sitewhere/sitewhere

Technical documentation

docs.aws.amazon.com/redshift

learn.microsoft.com/en-us/azure/search

docs.microsoft.com/azure/synapse-analytics

planetscale.com/docs

sitewhere1.sitewhere.io/index.html

Developer

Amazon (based on PostgreSQL)

Microsoft

PlanetScale

SiteWhere

Initial release

2012

2015

2016

2020

2010

Current release

License

Commercial or Open Source

commercial

Open Source

Common Public Attribution License Version 1.0

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

Server operating systems

hosted

Docker
Linux
macOS

Linux
OS X
Windows

Data scheme

yes

predefined scheme

Typing

predefined data types such as float or date

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

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

with proprietary extensions

APIs and other access methods

JDBC
ODBC

RESTful HTTP API

ADO.NET
JDBC
ODBC

ADO.NET
JDBC
MySQL protocol
ODBC

HTTP REST

Supported programming languages

All languages supporting JDBC/ODBC

C#
Java
JavaScript
Python

C#
Java
PHP

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

user defined functions

in Python

Transact SQL

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

Sharding, horizontal partitioning

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Implicit feature of the cloud service

yes

Multi-source replication
Source-replica replication

selectable replication factor

based on HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency across shards
Immediate Consistency within a shard

Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

docs.microsoft.com/en-us/azure/synapse-analytics/sql-data-warehouse/sql-data-warehouse-table-constraints

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

ACID at shard level

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

fine grained access rights according to SQL-standard

yes

using Azure authentication

yes

Users with fine-grained authorization concept

no user groups or roles

Users with fine-grained authorization concept

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.