DBMS > Memcached vs. mSQL vs. Oracle Berkeley DB vs. Snowflake vs. SQream DB

System Properties Comparison Memcached vs. mSQL vs. Oracle Berkeley DB vs. Snowflake vs. SQream DB

Editorial information provided by DB-Engines

Name

Description

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

mSQL (Mini SQL) is a simple and lightweight RDBMS

Widely used in-process key-value store

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

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

Primary database model

Key-value store

Relational DBMS

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Relational DBMS

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

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

Score	1.26
Rank	#163	Overall
	#74	Relational DBMS

Score	1.88
Rank	#130	Overall
	#23	Key-value stores
	#3	Native XML DBMS

Score	133.72
Rank	#7	Overall
	#5	Relational DBMS

Score	0.62
Rank	#234	Overall
	#109	Relational DBMS

Website

www.memcached.org

hughestech.com.au/products/msql

www.oracle.com/database/technologies/related/berkeleydb.html

www.snowflake.com

sqream.com

Technical documentation

github.com/memcached/memcached/wiki

docs.oracle.com/cd/E17076_05/html/index.html

docs.snowflake.net/manuals/index.html

docs.sqream.com

Developer

Danga Interactive

originally developed by Brad Fitzpatrick for LiveJournal

Hughes Technologies

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Snowflake Computing Inc.

SQream Technologies

Initial release

2003

1994

2014

2017

Current release

1.6.29, June 2024

4.4, October 2021

18.1.40, May 2020

2022.1.6, December 2022

License

Commercial or Open Source

Open Source

BSD license

commercial

free licenses can be provided

Open Source

commercial license available

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

C, Java, C++ (depending on the Berkeley DB edition)

C++, CUDA, Haskell, Java, Scala

Server operating systems

FreeBSD
Linux
OS X
Unix
Windows

AIX
HP-UX
Linux
OS X
Solaris SPARC/x86
Windows

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

hosted

Linux

Data scheme

schema-free

yes

schema-free

yes

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

yes

Typing

predefined data types such as float or date

yes

yes, ANSI Standard SQL Types

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

only with the Berkeley DB XML edition

yes

Secondary indexes

yes

SQL

Support of SQL

A subset of ANSI SQL is implemented

no subqueries, aggregate functions, views, foreign keys, triggers

yes

SQL interfaced based on SQLite is available

yes

APIs and other access methods

Proprietary protocol

JDBC
ODBC

CLI Client
JDBC
ODBC

.Net
JDBC
ODBC

Supported programming languages

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

C
C++
Delphi
Java
Perl
PHP
Tcl

.Net

Figaro is a .Net framework assembly that extends Berkeley DB XML into an embeddable database engine for .NET
others

Third-party libraries to manipulate Berkeley DB files are available for many languages
C
C#
C++
Java
JavaScript (Node.js)

3rd party binding
Perl
Python
Tcl

JavaScript (Node.js)
Python

C++
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

user defined functions in Python

Triggers

yes

only for the SQL API

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

none

yes

horizontal and vertical partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

Repcached, a Memcached patch, provides this functionallity

none

Source-replica replication

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

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

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

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.