DBMS > DataFS vs. IBM Cloudant vs. Quasardb vs. Snowflake

System Properties Comparison DataFS vs. IBM Cloudant vs. Quasardb vs. Snowflake

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

All data is stored inside objects which are linked by so-called link attributes. Objects consist of classes which can be extended and de-extended at runtime. Graphs can be defined with a struct.

Database as a Service offering based on Apache CouchDB

Distributed, high-performance timeseries database

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

Primary database model

Secondary database models

Graph DBMS

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

Score	0.09
Rank	#360	Overall
	#17	Object oriented DBMS

Score	2.75
Rank	#104	Overall
	#19	Document stores

Score	0.21
Rank	#322	Overall
	#29	Time Series DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

newdatabase.com

www.ibm.com/products/cloudant

quasar.ai

www.snowflake.com

Technical documentation

dev.mobiland.com/Overview.xsp

cloud.ibm.com/docs/Cloudant

doc.quasar.ai/master

docs.snowflake.net/manuals/index.html

Developer

Mobiland AG

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

quasardb

Snowflake Computing Inc.

Initial release

2018

2010

2009

2014

Current release

1.1.263, October 2022

3.14.1, January 2024

License

Commercial or Open Source

commercial

Free community edition, Non-profit organizations and non-commercial usage are eligible for free licenses

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

Erlang

C++

Server operating systems

Windows

hosted

BSD
Linux
OS X
Windows

hosted

Data scheme

Classes, Structs, and Lists are written in proprietary DataTypeDefinitionLanguage (.dtdl) and Objects consisting of those are written in proprietary DataAccessDefinitionLanguage (.dadl)

schema-free

yes

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

Typing

predefined data types such as float or date

yes

integer and binary

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

with tags

SQL

Support of SQL

SQL-like query language

yes

APIs and other access methods

.NET Client API
Proprietary client DLL
WinRT client

RESTful HTTP/JSON API

HTTP API

CLI Client
JDBC
ODBC

Supported programming languages

.Net
C
C#
C++
VB.Net

C#
Java
JavaScript
Objective-C
PHP
Ruby

.Net
C
C#
C++
Go
Java
JavaScript (Node.js)
PHP
Python
R

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

View functions (Map-Reduce) in JavaScript

user defined functions

Triggers

no, except callback-events from server when changes happened

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Proprietary Sharding system

Sharding

consistent hashing

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

Source-replica replication with selectable replication factor

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

with Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

atomic operations within a document possible

ACID

Concurrency

Support for concurrent manipulation of data

yes

Optimistic locking

yes

Durability

Support for making data persistent

yes

by using LevelDB

yes

In-memory capabilities

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

yes

Transient mode

User concepts

Access control

Windows-Profile

Access rights for users can be defined per database

Cryptographically strong user authentication and audit trail

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.