DBMS > Citus vs. IBM Cloudant vs. IBM Db2 warehouse vs. Microsoft Access vs. Snowflake

System Properties Comparison Citus vs. IBM Cloudant vs. IBM Db2 warehouse vs. Microsoft Access vs. Snowflake

Editorial information provided by DB-Engines

Name

Description

Scalable hybrid operational and analytics RDBMS for big data use cases based on PostgreSQL

Database as a Service offering based on Apache CouchDB

Cloud-based data warehousing service

Microsoft Access combines a backend RDBMS (JET / ACE Engine) with a GUI frontend for data manipulation and queries.

The Access frontend is often used for accessing other datasources (DBMS, Excel, etc.)

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

Primary database model

Relational DBMS

Document store

Relational DBMS

Secondary database models

Document store

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

Score	2.15
Rank	#117	Overall
	#56	Relational DBMS

Score	2.75
Rank	#104	Overall
	#19	Document stores

Score	1.37
Rank	#160	Overall
	#74	Relational DBMS

Score	101.16
Rank	#11	Overall
	#8	Relational DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

www.citusdata.com

www.ibm.com/products/cloudant

www.ibm.com/products/db2/warehouse

www.microsoft.com/en-us/microsoft-365/access

www.snowflake.com

Technical documentation

docs.citusdata.com

cloud.ibm.com/docs/Cloudant

developer.microsoft.com/en-us/access

docs.snowflake.net/manuals/index.html

Developer

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

IBM

Microsoft

Snowflake Computing Inc.

Initial release

2010

2014

1992

2014

Current release

8.1, December 2018

1902 (16.0.11328.20222), March 2019

License

Commercial or Open Source

Open Source

AGPL, commercial license also available

commercial

Bundled with Microsoft Office

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

Linux

hosted

Windows

Not a real database server, but making use of DLLs

hosted

Data scheme

yes

schema-free

yes

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

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

specific XML type available, but no XML query functionality

Import/export of XML data possible

yes

Secondary indexes

yes

SQL

Support of SQL

yes

standard, with numerous extensions

yes

but not compliant to any SQL standard

yes

APIs and other access methods

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

RESTful HTTP/JSON API

.NET Client API
JDBC
ODBC
OLE DB

ADO.NET
DAO
ODBC
OLE DB

CLI Client
JDBC
ODBC

Supported programming languages

.Net
C
C++
Delphi
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

C#
Java
JavaScript
Objective-C
PHP
Ruby

Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby

C
C#
C++
Delphi
Java (JDBC-ODBC)
VBA
Visual Basic.NET

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

realized in proprietary language PL/pgSQL or with common languages like Perl, Python, Tcl etc.

View functions (Map-Reduce) in JavaScript

PL/SQL, SQL PL

yes

since Access 2010 using the ACE-engine

user defined functions

Triggers

yes

since Access 2010 using the ACE-engine

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

other methods possible by using 3rd party extensions

Multi-source replication
Source-replica replication

yes

none

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

yes

Transaction concepts

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

ACID

atomic operations within a document possible

ACID

but no files for transaction logging

ACID

Concurrency

Support for concurrent manipulation of data

yes

Optimistic locking

yes

Durability

Support for making data persistent

yes

but no files for transaction logging

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

fine grained access rights according to SQL-standard

Access rights for users can be defined per database

fine grained access rights according to SQL-standard

a simple user-level security was built in till version Access 2003

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.