DBMS > Axibase vs. Datomic vs. FatDB vs. GeoSpock vs. Snowflake

System Properties Comparison Axibase vs. Datomic vs. FatDB vs. GeoSpock vs. Snowflake

Editorial information provided by DB-Engines

Name

FatDB/FatCloud has ceased operations as a company with February 2014. FatDB is discontinued and excluded from the ranking.

GeoSpock seems to be discontinued. Therefore it will be excluded from the DB-Engines ranking.

Description

Scalable TimeSeries DBMS based on HBase with integrated rule engine and visualization

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

A .NET NoSQL DBMS that can integrate with and extend SQL Server.

Spatial and temporal data processing engine for extreme data scale

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

Primary database model

Time Series DBMS

Relational DBMS

Document store
Key-value store

Relational DBMS

Secondary database models

Time Series DBMS

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

Score	0.29
Rank	#292	Overall
	#25	Time Series DBMS

Score	1.59
Rank	#150	Overall
	#69	Relational DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

axibase.com/docs/atsd/finance

www.datomic.com

geospock.com

www.snowflake.com

Technical documentation

docs.datomic.com

docs.snowflake.net/manuals/index.html

Developer

Axibase Corporation

Cognitect

FatCloud

GeoSpock

Snowflake Computing Inc.

Initial release

2013

2012

2014

Current release

15585

1.0.6735, June 2023

2.0, September 2019

License

Commercial or Open Source

commercial

Community Edition (single node) is free, Enterprise Edition (distributed) is paid

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

Java, Clojure

Java, Javascript

Server operating systems

Linux

All OS with a Java VM

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

short, integer, long, float, double, decimal, string

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

temporal, categorical

SQL

Support of SQL

SQL-like query language

Via inetgration in SQL Server

ANSI SQL for query only (using Presto)

yes

APIs and other access methods

JDBC
Proprietary protocol (Network API)
RESTful HTTP API

RESTful HTTP API

.NET Client API
LINQ
RESTful HTTP API
RPC
Windows WCF Bindings

JDBC

CLI Client
JDBC
ODBC

Supported programming languages

Go
Java
PHP
Python
R
Ruby

Clojure
Java

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

Transaction Functions

yes

via applications

user defined functions

Triggers

yes

By using transaction functions

yes

via applications

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

But extensive use of caching in the application peers

Sharding

Automatic sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

none

But extensive use of caching in the application peers

selectable replication factor

yes

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

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

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

User concepts

Access control

Can implement custom security layer via applications

Access rights for users can be defined per table

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.