DBMS > AgensGraph vs. CouchDB vs. EXASOL vs. Snowflake

System Properties Comparison AgensGraph vs. CouchDB vs. EXASOL vs. Snowflake

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

A native JSON - document store inspired by Lotus Notes, scalable from globally distributed server-clusters down to mobile phones.

High-performance, in-memory, MPP database specifically designed for in-memory analytics.

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

Primary database model

Graph DBMS
Relational DBMS

Document store

Relational DBMS

Secondary database models

Spatial DBMS

using the Geocouch extension

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

Score	0.16
Rank	#333	Overall
	#30	Graph DBMS
	#146	Relational DBMS

Score	10.26
Rank	#45	Overall
	#7	Document stores

Score	2.25
Rank	#120	Overall
	#57	Relational DBMS

Score	123.20
Rank	#9	Overall
	#6	Relational DBMS

Website

bitnine.net/agensgraph

couchdb.apache.org

www.exasol.com

www.snowflake.com

Technical documentation

bitnine.net/documentation

docs.couchdb.org/en/stable

www.exasol.com/resources

docs.snowflake.net/manuals/index.html

Developer

Bitnine Global Inc.

Apache Software Foundation

Apache top-level project, originally developed by Damien Katz, a former Lotus Notes developer

Exasol

Snowflake Computing Inc.

Initial release

2016

2005

2000

2014

Current release

2.1, December 2018

3.3.3, December 2023

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

Apache version 2

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

Server operating systems

Linux
OS X
Windows

Android
BSD
Linux
OS X
Solaris
Windows

hosted

Data scheme

depending on used data model

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

Secondary indexes

yes

via views

yes

SQL

Support of SQL

yes

APIs and other access methods

Cypher Query Language
JDBC

RESTful HTTP/JSON API

.Net
JDBC
ODBC
WebSocket

CLI Client
JDBC
ODBC

Supported programming languages

C
Java
JavaScript
Python

C
C#
ColdFusion
Erlang
Haskell
Java
JavaScript
Lisp
Lua
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
Ruby
Smalltalk

Java
Lua
Python
R

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

View functions in JavaScript

user defined functions

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

no, but can be realized using table inheritance

Sharding

improved architecture with release 2.0

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Multi-source replication
Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

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 single document possible

ACID

Concurrency

Support for concurrent manipulation of data

yes

strategy: 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.

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Access rights for users can be defined per database

Access rights for users, groups and roles according to SQL-standard

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.