DBMS > Blueflood vs. LevelDB vs. Microsoft Azure Cosmos DB vs. Valentina Server vs. WakandaDB

System Properties Comparison Blueflood vs. LevelDB vs. Microsoft Azure Cosmos DB vs. Valentina Server vs. WakandaDB

Editorial information provided by DB-Engines

Name

Description

Scalable TimeSeries DBMS based on Cassandra

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

Globally distributed, horizontally scalable, multi-model database service

Object-relational database and reports server

WakandaDB is embedded in a server that provides a REST API and a server-side javascript engine to access data

Primary database model

Time Series DBMS

Key-value store

Document store
Graph DBMS
Key-value store
Wide column store

Relational DBMS

Object oriented DBMS

Secondary database models

Spatial DBMS

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

Score	0.06
Rank	#353	Overall
	#34	Time Series DBMS

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

Score	29.04
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Score	0.17
Rank	#327	Overall
	#145	Relational DBMS

Score	0.03
Rank	#364	Overall
	#17	Object oriented DBMS

Website

blueflood.io

github.com/google/leveldb

azure.microsoft.com/services/cosmos-db

www.valentina-db.net

wakanda.github.io

Technical documentation

github.com/rax-maas/blueflood/wiki

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

learn.microsoft.com/azure/cosmos-db

valentina-db.com/docs/dokuwiki/v5/doku.php

wakanda.github.io/doc

Developer

Rackspace

Google

Microsoft

Paradigma Software

Wakanda SAS

Initial release

2013

2011

2014

1999

2012

Current release

1.23, February 2021

5.7.5

2.7.0 (April 29, 2019), April 2019

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

BSD

commercial

Open Source

AGPLv3, extended commercial license available

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

C++

C++, JavaScript

Server operating systems

Linux
OS X

Illumos
Linux
OS X
Windows

hosted

Linux
OS X
Windows

Data scheme

predefined scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

JSON 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.

Secondary indexes

yes

All properties auto-indexed by default

yes

SQL

Support of SQL

SQL-like query language

yes

APIs and other access methods

HTTP REST

DocumentDB API
Graph API (Gremlin)
MongoDB API
RESTful HTTP API
Table API

ODBC

RESTful HTTP API

Supported programming languages

C++
Go
Java

3rd party binding
JavaScript (Node.js)

3rd party binding
Python

3rd party binding

.Net
C#
Java
JavaScript
JavaScript (Node.js)
MongoDB client drivers written for various programming languages
Python

.Net
C
C#
C++
Objective-C
PHP
Ruby
Visual Basic
Visual Basic.NET

JavaScript

Server-side scripts

Stored procedures

JavaScript

yes

Triggers

JavaScript

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

based on Cassandra

none

Sharding

Implicit feature of the cloud service

none

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

based on Cassandra

none

yes

Implicit feature of the cloud service

none

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Immediate Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

Multi-item ACID transactions with snapshot isolation within a partition

ACID

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.

yes

User concepts

Access control

Access rights can be defined down to the item level

fine grained access rights according to SQL-standard

yes

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.