DBMS > Amazon Aurora vs. Immudb vs. Microsoft SQL Server vs. PlanetScale vs. STSdb

System Properties Comparison Amazon Aurora vs. Immudb vs. Microsoft SQL Server vs. PlanetScale vs. STSdb

Editorial information provided by DB-Engines

Name

Description

MySQL and PostgreSQL compatible cloud service by Amazon

An open source immutable (append-only) database with cryptographic verification which makes it tamper-resistant and fully auditable.

Microsofts flagship relational DBMS

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

Key-Value Store with special method for indexing

optimized for high performance using a special indexing method

Primary database model

Secondary database models

Document store

Relational DBMS

Document store
Graph DBMS
Spatial DBMS

Document store
Spatial DBMS

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

Score	7.91
Rank	#50	Overall
	#32	Relational DBMS

Score	0.24
Rank	#305	Overall
	#43	Key-value stores

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	1.59
Rank	#151	Overall
	#70	Relational DBMS

Score	0.04
Rank	#360	Overall
	#52	Key-value stores

Website

aws.amazon.com/rds/aurora

github.com/codenotary/immudb
immudb.io

www.microsoft.com/en-us/sql-server

planetscale.com

github.com/STSSoft/STSdb4

Technical documentation

docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/CHAP_Aurora.html

docs.immudb.io

learn.microsoft.com/en-US/sql/sql-server

planetscale.com/docs

Developer

Amazon

Codenotary

Microsoft

PlanetScale

STS Soft SC

Initial release

2015

2020

1989

2020

2011

Current release

1.2.3, April 2022

SQL Server 2022, November 2022

4.0.8, September 2015

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

commercial

restricted free version is available

commercial

Open Source

GPLv2, commercial license available

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++

Server operating systems

hosted

BSD
Linux
macOS
Solaris
Windows
z/OS

Linux
Windows

Docker
Linux
macOS

Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

primitive types and user defined types (classes)

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

SQL

Support of SQL

yes

SQL-like syntax

yes

with proprietary extensions

APIs and other access methods

ADO.NET
JDBC
ODBC

gRPC protocol
PostgreSQL wire protocol

ADO.NET
JDBC
ODBC
OLE DB
Tabular Data Stream (TDS)

ADO.NET
JDBC
MySQL protocol
ODBC

.NET Client API

Supported programming languages

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

.Net
Go
Java
JavaScript (Node.js)
Python

C#
C++
Delphi
Go
Java
JavaScript (Node.js)
PHP
Python
R
Ruby
Visual Basic

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

C#
Java

Server-side scripts

Stored procedures

yes

Transact SQL, .NET languages, R, Python and (with SQL Server 2019) Java

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

Sharding

tables can be distributed across several files (horizontal partitioning); sharding through federation

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes, but depending on the SQL-Server Edition

Multi-source replication
Source-replica replication

none

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

Foreign keys

Referential integrity

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

Users with fine-grained authorization concept

no user groups or roles

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.