DBMS > Memcached vs. Rockset vs. Snowflake vs. Transbase vs. XTDB

System Properties Comparison Memcached vs. Rockset vs. Snowflake vs. Transbase vs. XTDB

Editorial information provided by DB-Engines

Name

Description

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

A scalable, reliable search and analytics service in the cloud, built on RocksDB

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

A resource-optimized, high-performance, universally applicable RDBMS

A general purpose database with bitemporal SQL and Datalog and graph queries

Primary database model

Secondary database models

Relational DBMS
Search engine

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

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

Score	0.79
Rank	#211	Overall
	#35	Document stores

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	0.11
Rank	#341	Overall
	#150	Relational DBMS

Score	0.11
Rank	#343	Overall
	#46	Document stores

Website

www.memcached.org

rockset.com

www.snowflake.com

www.transaction.de/en/products/transbase.html

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

github.com/memcached/memcached/wiki

docs.rockset.com

docs.snowflake.net/manuals/index.html

www.transaction.de/en/products/transbase/features.html

www.xtdb.com/docs

Developer

Danga Interactive

originally developed by Brad Fitzpatrick for LiveJournal

Rockset

Snowflake Computing Inc.

Transaction Software GmbH

Juxt Ltd.

Initial release

2003

2019

2014

1987

2019

Current release

1.6.25, March 2024

Transbase 8.3, 2022

1.19, September 2021

License

Commercial or Open Source

Open Source

BSD license

commercial

free development license

Open Source

MIT License

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

C and C++

Clojure

Server operating systems

FreeBSD
Linux
OS X
Unix
Windows

hosted

FreeBSD
Linux
macOS
Solaris
Windows

All OS with a Java 8 (and higher) VM
Linux

Data scheme

schema-free

yes

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

yes

schema-free

Typing

predefined data types such as float or date

dynamic typing

yes

yes, extensible-data-notation format

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.

ingestion from XML files supported

yes

Secondary indexes

all fields are automatically indexed

yes

SQL

Support of SQL

Read-only SQL queries, including JOINs

yes

limited SQL, making use of Apache Calcite

APIs and other access methods

Proprietary protocol

HTTP REST

CLI Client
JDBC
ODBC

ADO.NET
JDBC
ODBC
Proprietary native API

HTTP REST
JDBC

Supported programming languages

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

Go
Java
JavaScript (Node.js)
Python

JavaScript (Node.js)
Python

C
C#
C++
Java
JavaScript
Kotlin
Objective-C
PHP
Python

Clojure
Java

Server-side scripts

Stored procedures

user defined functions

yes

Triggers

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

none

Automatic sharding

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

Repcached, a Memcached patch, provides this functionallity

yes

Source-replica replication

yes, each node contains all data

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

yes

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

In-memory capabilities

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

User concepts

Access control

yes

using SASL (Simple Authentication and Security Layer) protocol

Access rights for users and organizations can be defined via Rockset console

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

fine grained access rights according to SQL-standard

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.