DBMS > Datomic vs. EXASOL vs. Google Cloud Datastore vs. PostGIS vs. Snowflake

System Properties Comparison Datomic vs. EXASOL vs. Google Cloud Datastore vs. PostGIS 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

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

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

Spatial extension of PostgreSQL

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

Primary database model

Secondary database models

Relational DBMS

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

Score	1.66
Rank	#144	Overall
	#66	Relational DBMS

Score	1.76
Rank	#139	Overall
	#62	Relational DBMS

Score	4.36
Rank	#72	Overall
	#12	Document stores

Score	21.72
Rank	#29	Overall
	#1	Spatial DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

www.datomic.com

www.exasol.com

cloud.google.com/datastore

postgis.net

www.snowflake.com

Technical documentation

docs.datomic.com

www.exasol.com/resources

cloud.google.com/datastore/docs

postgis.net/documentation

docs.snowflake.net/manuals/index.html

Developer

Cognitect

Exasol

Google

Snowflake Computing Inc.

Initial release

2012

2000

2008

2005

2014

Current release

1.0.7075, December 2023

3.4.2, February 2024

License

Commercial or Open Source

commercial

limited edition free

commercial

Open Source

GPL v2.0

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

Server operating systems

All OS with a Java VM

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

yes, details here

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

yes

SQL-like query language (GQL)

yes

APIs and other access methods

RESTful HTTP API

.Net
JDBC
ODBC
WebSocket

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

CLI Client
JDBC
ODBC

Supported programming languages

Clojure
Java

Java
Lua
Python
R

.Net
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

Transaction Functions

user defined functions

using Google App Engine

user defined functions

Triggers

By using transaction functions

yes

Callbacks using the Google Apps Engine

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

yes

based on PostgreSQL

yes

Replication methods

Methods for redundantly storing data on multiple nodes

none

But extensive use of caching in the application peers

Multi-source replication using Paxos

yes

based on PostgreSQL

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Hadoop integration

yes

using Google Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

Immediate Consistency

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

yes

Transaction concepts

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

ACID

Concurrency

Support for concurrent manipulation of data

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

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

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

yes

based on PostgreSQL

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.