DBMS > Amazon Aurora vs. KairosDB vs. Machbase Neo vs. Memcached vs. Snowflake

System Properties Comparison Amazon Aurora vs. KairosDB vs. Machbase Neo vs. Memcached vs. Snowflake

Editorial information provided by DB-Engines

Name

Description

MySQL and PostgreSQL compatible cloud service by Amazon

Distributed Time Series DBMS based on Cassandra or H2

TimeSeries DBMS for AIoT and BigData

In-memory key-value store, originally intended for caching

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

Primary database model

Secondary database models

Document store

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

Score	7.57
Rank	#51	Overall
	#32	Relational DBMS

Score	0.67
Rank	#233	Overall
	#20	Time Series DBMS

Score	0.17
Rank	#337	Overall
	#30	Time Series DBMS

Score	18.08
Rank	#32	Overall
	#4	Key-value stores

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

aws.amazon.com/rds/aurora

github.com/kairosdb/kairosdb

machbase.com

www.memcached.org

www.snowflake.com

Technical documentation

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

kairosdb.github.io

machbase.com/dbms

github.com/memcached/memcached/wiki

docs.snowflake.net/manuals/index.html

Developer

Amazon

Machbase

Danga Interactive

originally developed by Brad Fitzpatrick for LiveJournal

Snowflake Computing Inc.

Initial release

2015

2013

2003

2014

Current release

1.2.2, November 2018

V8.0, August 2023

1.6.27, May 2024

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

commercial

free test version available

Open Source

BSD license

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

Linux
macOS
Windows

FreeBSD
Linux
OS X
Unix
Windows

hosted

Data scheme

yes

schema-free

yes

schema-free

yes

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

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

Secondary indexes

yes

SQL

Support of SQL

yes

SQL-like query language

yes

APIs and other access methods

ADO.NET
JDBC
ODBC

Graphite protocol
HTTP REST
Telnet API

gRPC
HTTP REST
JDBC
MQTT (Message Queue Telemetry Transport)
ODBC

Proprietary protocol

CLI Client
JDBC
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

Java
JavaScript

Node.js
PHP
Python

C
C#
C++
Go
Java
JavaScript
PHP

via ODBC
Python
R

via ODBC
Scala

.Net
C
C++
ColdFusion
Erlang
Java
Lisp
Lua
OCaml
Perl
PHP
Python
Ruby

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

user defined functions

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

Sharding

based on Cassandra

Sharding

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

selectable replication factor

based on Cassandra

selectable replication factor

none

Repcached, a Memcached patch, provides this functionallity

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

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

In-memory capabilities

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

yes

volatile and lookup table

User concepts

Access control

fine grained access rights according to SQL-standard

simple password-based access control

yes

using SASL (Simple Authentication and Security Layer) protocol

Users with fine-grained authorization concept, user roles and pluggable 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.