DBMS > Datomic vs. EXASOL vs. PostGIS vs. Snowflake vs. Sqrrl

System Properties Comparison Datomic vs. EXASOL vs. PostGIS vs. Snowflake vs. Sqrrl

Editorial information provided by DB-Engines

Name

Sqrrl has been acquired by Amazon and became a part of Amazon Web Services. It has been removed from the DB-Engines ranking.

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.

Spatial extension of PostgreSQL

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

Adaptable, secure NoSQL built on Apache Accumulo

Primary database model

Relational DBMS

Spatial DBMS

Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

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	21.72
Rank	#29	Overall
	#1	Spatial DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

sqrrl.com

Technical documentation

docs.datomic.com

www.exasol.com/resources

postgis.net/documentation

docs.snowflake.net/manuals/index.html

Developer

Cognitect

Exasol

Snowflake Computing Inc.

Amazon

originally Sqrrl Data, Inc.

Initial release

2012

2000

2005

2014

2012

Current release

1.0.6735, June 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

Java

Server operating systems

All OS with a Java VM

hosted

Linux

Data scheme

yes

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

schema-free

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

yes

APIs and other access methods

RESTful HTTP API

.Net
JDBC
ODBC
WebSocket

CLI Client
JDBC
ODBC

Accumulo Shell
Java API
JDBC
ODBC
RESTful HTTP API
Thrift

Supported programming languages

Clojure
Java

Java
Lua
Python
R

JavaScript (Node.js)
Python

Actionscript
C

using GLib
C#
C++
Cocoa
Delphi
Erlang
Go
Haskell
Java
JavaScript
OCaml
Perl
PHP
Python
Ruby
Smalltalk

Server-side scripts

Stored procedures

yes

Transaction Functions

user defined functions

Triggers

By using transaction functions

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

Sharding

making use of Hadoop

Replication methods

Methods for redundantly storing data on multiple nodes

none

But extensive use of caching in the application peers

yes

based on PostgreSQL

yes

selectable replication factor

making use of Hadoop

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Hadoop integration

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Document store kept consistent with combination of global timestamping, row-level transactions, and server-side consistency resolution.

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Atomic updates per row, document, or graph entity

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

yes

based on PostgreSQL

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

Cell-level Security, Data-Centric Security, Role-Based Access Control (RBAC), Attribute-Based Access Control (ABAC)

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.