DBMS > Amazon Aurora vs. Ingres vs. Snowflake vs. Vitess

System Properties Comparison Amazon Aurora vs. Ingres vs. Snowflake vs. Vitess

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

MySQL and PostgreSQL compatible cloud service by Amazon

Well established RDBMS

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

Scalable, distributed, cloud-native DBMS, extending MySQL

Primary database model

Relational DBMS

Secondary database models

Document store

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	4.11
Rank	#81	Overall
	#44	Relational DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	0.82
Rank	#209	Overall
	#97	Relational DBMS

Website

aws.amazon.com/rds/aurora

www.actian.com/databases/ingres

www.snowflake.com

vitess.io

Technical documentation

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

docs.actian.com/ingres

docs.snowflake.net/manuals/index.html

vitess.io/docs

Developer

Amazon

Actian Corporation

Snowflake Computing Inc.

The Linux Foundation, PlanetScale

Initial release

2015

1974

originally developed at University Berkely in early 1970s

2014

2013

Current release

11.2, May 2022

15.0.2, December 2022

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0, commercial licenses 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

Server operating systems

hosted

AIX
HP Open VMS
HP-UX
Linux
Solaris
Windows

hosted

Docker
Linux
macOS

Data scheme

yes

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

yes

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.

yes

but tools for importing/exporting data from/to XML-files available

yes

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

APIs and other access methods

ADO.NET
JDBC
ODBC

.NET Client API
JDBC
ODBC
proprietary protocol (OpenAPI)

CLI Client
JDBC
ODBC

ADO.NET
JDBC
MySQL protocol
ODBC

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

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

yes

user defined functions

yes

proprietary syntax

Triggers

yes

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

Ingres Star to access multiple databases simultaneously

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Ingres Replicator

yes

Multi-source replication
Source-replica replication

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

MVCC

yes

table locks or row locks depending on storage engine

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

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.