DBMS > Memcached vs. Snowflake vs. SQream DB vs. TerarkDB vs. VoltDB

System Properties Comparison Memcached vs. Snowflake vs. SQream DB vs. TerarkDB vs. VoltDB

Editorial information provided by DB-Engines

Name

Description

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

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

a GPU-based, columnar RDBMS for big data analytics workloads

A key-value store forked from RocksDB with advanced compression algorithms. It can be used standalone or as a storage engine for MySQL and MongoDB

Distributed In-Memory NewSQL RDBMS

Used for OLTP applications with a high frequency of relatively simple transactions, that can hold all their data in memory

Primary database model

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

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

Score	133.72
Rank	#7	Overall
	#5	Relational DBMS

Score	0.62
Rank	#234	Overall
	#109	Relational DBMS

Score	0.00
Rank	#385	Overall
	#61	Key-value stores

Score	1.38
Rank	#156	Overall
	#72	Relational DBMS

Website

www.memcached.org

www.snowflake.com

sqream.com

github.com/bytedance/terarkdb

www.voltdb.com

Technical documentation

github.com/memcached/memcached/wiki

docs.snowflake.net/manuals/index.html

docs.sqream.com

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

docs.voltdb.com

Developer

Danga Interactive

originally developed by Brad Fitzpatrick for LiveJournal

Snowflake Computing Inc.

SQream Technologies

ByteDance, originally Terark

VoltDB Inc.

Initial release

2003

2014

2017

2016

2010

Current release

1.6.29, June 2024

2022.1.6, December 2022

11.3, April 2022

License

Commercial or Open Source

Open Source

BSD license

commercial

restricted open source version available

Open Source

AGPL for Community Edition, commercial license for Enterprise, AWS, and Pro Editions

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++, CUDA, Haskell, Java, Scala

C++

Java, C++

Server operating systems

FreeBSD
Linux
OS X
Unix
Windows

hosted

Linux

Linux
OS X

for development

Data scheme

schema-free

yes

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

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

yes, ANSI Standard SQL 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

only a subset of SQL 99

APIs and other access methods

Proprietary protocol

CLI Client
JDBC
ODBC

.Net
JDBC
ODBC

C++ API
Java API

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

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

JavaScript (Node.js)
Python

C++
Java
JavaScript (Node.js)
Python

C++
Java

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

user defined functions

user defined functions in Python

Java

Triggers

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

none

yes

horizontal and vertical partitioning

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

Repcached, a Memcached patch, provides this functionallity

yes

none

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

Foreign keys

Referential integrity

yes

FOREIGN KEY constraints are not supported

Transaction concepts

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

ACID

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes

Snapshots and command logging

In-memory capabilities

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

yes

User concepts

Access control

yes

using SASL (Simple Authentication and Security Layer) protocol

Users with fine-grained authorization concept, user roles and pluggable authentication

Users and roles with access to stored procedures

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.