DBMS > Datomic vs. GridGain vs. IBM Cloudant vs. SAP IQ vs. Snowflake

System Properties Comparison Datomic vs. GridGain vs. IBM Cloudant vs. SAP IQ vs. Snowflake

Editorial information provided by DB-Engines

Name

Description

Datomic builds on immutable values, supports point-in-time queries and uses 3rd party systems for durability

GridGain is an in-memory computing platform, built on Apache Ignite

Database as a Service offering based on Apache CouchDB

Columnar RDBMS optimized for Big Data analytics

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

Primary database model

Relational DBMS

Key-value store
Relational DBMS

Document store

Relational DBMS

column-oriented

Relational DBMS

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

Score	1.59
Rank	#150	Overall
	#69	Relational DBMS

Score	1.47
Rank	#154	Overall
	#26	Key-value stores
	#72	Relational DBMS

Score	2.68
Rank	#106	Overall
	#20	Document stores

Score	2.75
Rank	#104	Overall
	#53	Relational DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

www.datomic.com

www.gridgain.com

www.ibm.com/products/cloudant

www.sap.com/products/technology-platform/sybase-iq-big-data-management.html

www.snowflake.com

Technical documentation

docs.datomic.com

www.gridgain.com/docs/index.html

cloud.ibm.com/docs/Cloudant

help.sap.com/docs/SAP_IQ

docs.snowflake.net/manuals/index.html

Developer

Cognitect

GridGain Systems, Inc.

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

SAP, formerly Sybase

Snowflake Computing Inc.

Initial release

2012

2007

2010

1994

2014

Current release

1.0.6735, June 2023

GridGain 8.5.1

16.1 SPS04, April 2019

License

Commercial or Open Source

commercial

limited edition free

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

Java, Clojure

Java, C++, .Net

Erlang

Server operating systems

All OS with a Java VM

Linux
OS X
Solaris
Windows

hosted

AIX
HP-UX
Linux
Solaris
Windows

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

Secondary indexes

yes

SQL

Support of SQL

ANSI-99 for query and DML statements, subset of DDL

yes

APIs and other access methods

RESTful HTTP API

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

RESTful HTTP/JSON API

ADO.NET
JDBC
ODBC
RESTful HTTP API

CLI Client
JDBC
ODBC

Supported programming languages

Clojure
Java

C#
C++
Java
PHP
Python
Ruby
Scala

C#
Java
JavaScript
Objective-C
PHP
Ruby

C
C#
C++
Java
Perl
PHP
Python
Ruby

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

Transaction Functions

yes (compute grid and cache interceptors can be used instead)

View functions (Map-Reduce) in JavaScript

yes

user defined functions

Triggers

By using transaction functions

yes (cache interceptors and events)

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

none

But extensive use of caching in the application peers

Sharding

shared disk or shared nothing architectures with SAP IQ Multiplexer

yes

Replication methods

Methods for redundantly storing data on multiple nodes

none

But extensive use of caching in the application peers

yes (replicated cache)

Multi-source replication
Source-replica replication

SAP/Sybase Replication Server

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes (compute grid and hadoop accelerator)

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Optimistic locking

yes

Durability

Support for making data persistent

yes

using external storage systems (e.g. Cassandra, DynamoDB, PostgreSQL, Couchbase and others)

yes

In-memory capabilities

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

yes

recommended only for testing and development

yes

User concepts

Access control

Security Hooks for custom implementations

Access rights for users can be defined per database

fine grained access rights 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.