DBMS > Amazon Aurora vs. Snowflake vs. SQL.JS vs. TimescaleDB vs. VelocityDB

System Properties Comparison Amazon Aurora vs. Snowflake vs. SQL.JS vs. TimescaleDB vs. VelocityDB

Editorial information provided by DB-Engines

Name

Description

MySQL and PostgreSQL compatible cloud service by Amazon

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

Port of SQLite to JavaScript

A time series DBMS optimized for fast ingest and complex queries, based on PostgreSQL

A .NET Object Database that can be embedded/distributed and extended to a graph data model (VelocityGraph)

Primary database model

Relational DBMS

Time Series DBMS

Graph DBMS
Object oriented DBMS

Secondary database models

Document store

Relational DBMS

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

Score	7.57
Rank	#51	Overall
	#32	Relational DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	0.63
Rank	#241	Overall
	#112	Relational DBMS

Score	4.46
Rank	#71	Overall
	#5	Time Series DBMS

Score	0.11
Rank	#354	Overall
	#37	Graph DBMS
	#15	Object oriented DBMS

Website

aws.amazon.com/rds/aurora

Technical documentation

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

docs.snowflake.net/manuals/index.html

sql.js.org/documentation/index.html

docs.timescale.com

velocitydb.com/UserGuide

Developer

Amazon

Snowflake Computing Inc.

Alon Zakai

enhancements implemented by others

Timescale

VelocityDB Inc

Initial release

2015

2014

2012

2017

2011

Current release

2.15.0, May 2024

7.x

License

Commercial or Open Source

commercial

Open Source

Apache 2.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

JavaScript

Server operating systems

hosted

server-less, requires a JavaScript environment (browser, Node.js)

Linux
OS X
Windows

Any that supports .NET

Data scheme

yes

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

yes

Typing

predefined data types such as float or date

yes

numerics, strings, booleans, arrays, JSON blobs, geospatial dimensions, currencies, binary data, other complex data 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

SQL

Support of SQL

yes

SQL-92 is not fully supported

yes

full PostgreSQL SQL syntax

APIs and other access methods

ADO.NET
JDBC
ODBC

CLI Client
JDBC
ODBC

JavaScript API

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

.Net

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

JavaScript (Node.js)
Python

JavaScript

.Net
C
C++
Delphi
Java

JDBC
JavaScript
Perl
PHP
Python
R
Ruby
Scheme
Tcl

.Net

Server-side scripts

Stored procedures

yes

user defined functions

user defined functions, PL/pgSQL, PL/Tcl, PL/Perl, PL/Python, PL/Java, PL/PHP, PL/R, PL/Ruby, PL/Scheme, PL/Unix shell

Triggers

yes

similar concept for controling cloud resources

yes

Callbacks are triggered when data changes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

yes

none

yes, across time and space (hash partitioning) attributes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

none

Source-replica replication with hot standby and reads on replicas

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

except by serializing a db to a file

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, user roles and pluggable authentication

fine grained access rights according to SQL-standard

Based on Windows 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.