DBMS > AgensGraph vs. IBM Cloudant vs. Snowflake vs. TimescaleDB

System Properties Comparison AgensGraph vs. IBM Cloudant vs. Snowflake vs. TimescaleDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Multi-model database supporting relational and graph data models and built upon PostgreSQL

Database as a Service offering based on Apache CouchDB

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

A time series DBMS optimized for fast ingest and complex queries, based on PostgreSQL

Primary database model

Graph DBMS
Relational DBMS

Document store

Relational DBMS

Time Series DBMS

Secondary database models

Relational DBMS

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

Score	0.23
Rank	#315	Overall
	#26	Graph DBMS
	#140	Relational DBMS

Score	2.75
Rank	#104	Overall
	#19	Document stores

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	4.46
Rank	#71	Overall
	#5	Time Series DBMS

Website

bitnine.net/agensgraph

www.ibm.com/products/cloudant

www.snowflake.com

www.timescale.com

Technical documentation

bitnine.net/documentation

cloud.ibm.com/docs/Cloudant

docs.snowflake.net/manuals/index.html

docs.timescale.com

Developer

Bitnine Global Inc.

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Snowflake Computing Inc.

Timescale

Initial release

2016

2010

2014

2017

Current release

2.1, December 2018

2.15.0, May 2024

License

Commercial or Open Source

Open Source

Apache License 2.0

commercial

Open Source

Apache 2.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

Erlang

Server operating systems

Linux
OS X
Windows

hosted

Linux
OS X
Windows

Data scheme

depending on used data model

schema-free

yes

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

yes

Typing

predefined data types such as float or date

yes

numerics, strings, booleans, arrays, JSON blobs, geospatial dimensions, currencies, binary data, other complex data 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

Secondary indexes

yes

SQL

Support of SQL

yes

full PostgreSQL SQL syntax

APIs and other access methods

Cypher Query Language
JDBC

RESTful HTTP/JSON API

CLI Client
JDBC
ODBC

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

Supported programming languages

C
Java
JavaScript
Python

C#
Java
JavaScript
Objective-C
PHP
Ruby

JavaScript (Node.js)
Python

.Net
C
C++
Delphi
Java

JDBC
JavaScript
Perl
PHP
Python
R
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

yes

View functions (Map-Reduce) in JavaScript

user defined functions

user defined functions, PL/pgSQL, PL/Tcl, PL/Perl, PL/Python, PL/Java, PL/PHP, PL/R, PL/Ruby, PL/Scheme, PL/Unix shell

Triggers

yes

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

no, but can be realized using table inheritance

Sharding

yes

yes, across time and space (hash partitioning) attributes

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Multi-source replication
Source-replica replication

yes

Source-replica replication with hot standby and reads on replicas

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

Concurrency

Support for concurrent manipulation of data

yes

Optimistic locking

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.

User concepts

Access control

fine grained access rights according to SQL-standard

Access rights for users can be defined per database

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

fine grained access rights according to SQL-standard

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.