DBMS > LevelDB vs. Riak KV vs. SAP Advantage Database Server vs. Snowflake vs. YottaDB

System Properties Comparison LevelDB vs. Riak KV vs. SAP Advantage Database Server vs. Snowflake vs. YottaDB

Editorial information provided by DB-Engines

Name

SAP Advantage Database Server seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

Embeddable fast key-value storage library that provides an ordered mapping from string keys to string values

Distributed, fault tolerant key-value store

Low-cost RDBMS with access to ISAM and FoxPro data structures

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

A fast and solid embedded Key-value store

Primary database model

Key-value store

with links between data sets and object tags for the creation of secondary indexes

Relational DBMS

Key-value store

Secondary database models

Relational DBMS

using the Octo plugin

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

Score	2.35
Rank	#111	Overall
	#19	Key-value stores

Score	4.10
Rank	#82	Overall
	#9	Key-value stores

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	0.20
Rank	#317	Overall
	#47	Key-value stores

Website

github.com/google/leveldb

www.sap.com/products/advantage-database-server.html

www.snowflake.com

yottadb.com

Technical documentation

github.com/google/leveldb/blob/main/doc/index.md

www.tiot.jp/riak-docs/riak/kv/latest

docs.snowflake.net/manuals/index.html

yottadb.com/resources/documentation

Developer

Google

OpenSource, formerly Basho Technologies

Sybase, SAP

Snowflake Computing Inc.

YottaDB, LLC

Initial release

2011

2009

1993

2014

2001

Current release

1.23, February 2021

3.2.0, December 2022

License

Commercial or Open Source

Open Source

BSD

Open Source

Apache version 2, commercial enterprise edition

commercial

Open Source

AGPL 3.0

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

Erlang

Server operating systems

Illumos
Linux
OS X
Windows

Linux
OS X

Linux
Windows

hosted

Docker
Linux

Data scheme

schema-free

yes

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

schema-free

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

restricted

yes

SQL

Support of SQL

yes

by using the Octo plugin

APIs and other access methods

HTTP API
Native Erlang Interface

.NET Client API
ADO.NET
JDBC
ODBC
OLE DB

CLI Client
JDBC
ODBC

PostgreSQL wire protocol

using the Octo plugin
Proprietary protocol

Supported programming languages

C++
Go
Java

3rd party binding
JavaScript (Node.js)

3rd party binding
Python

3rd party binding

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

Delphi
Perl
PHP

JavaScript (Node.js)
Python

C
Go
JavaScript (Node.js)
Lua
M
Perl
Python
Rust

Server-side scripts

Stored procedures

Erlang

yes

user defined functions

Triggers

yes

pre-commit hooks and post-commit hooks

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

no "single point of failure"

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

none

selectable replication factor

Multi-source replication

CONFLICT Trigger to resolve replication conflicts
Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

links between data sets can be stored

yes

Transaction concepts

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

ACID

optimistic locking

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

with automatic compression on writes

yes

In-memory capabilities

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

caching of (temporary) tables can be configured

yes

User concepts

Access control

yes, using Riak Security

fine grained access rights according to SQL-standard

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

Users and groups based on OS-security mechanisms

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.