DBMS > Datomic vs. FatDB vs. Hive vs. Snowflake vs. Yaacomo

System Properties Comparison Datomic vs. FatDB vs. Hive vs. Snowflake vs. Yaacomo

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.

Yaacomo seems to be discontinued and is removed from the DB-Engines ranking

Description

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.

data warehouse software for querying and managing large distributed datasets, built on Hadoop

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

OpenCL based in-memory RDBMS, designed for efficiently utilizing the hardware via parallel computing

Primary database model

Relational DBMS

Document store
Key-value store

Relational DBMS

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

Score	1.59
Rank	#150	Overall
	#69	Relational DBMS

Score	61.17
Rank	#18	Overall
	#12	Relational DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

www.datomic.com

hive.apache.org

www.snowflake.com

yaacomo.com

Technical documentation

docs.datomic.com

cwiki.apache.org/confluence/display/Hive/Home

docs.snowflake.net/manuals/index.html

Developer

Cognitect

FatCloud

Apache Software Foundation

initially developed by Facebook

Snowflake Computing Inc.

Q2WEB GmbH

Initial release

2012

2014

2009

Current release

1.0.6735, June 2023

3.1.3, April 2022

License

Commercial or Open Source

commercial

limited edition free

commercial

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

Java, Clojure

Java

Server operating systems

All OS with a Java VM

Windows

All OS with a Java VM

hosted

Android
Linux
Windows

Data scheme

yes

schema-free

yes

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

yes

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

Via inetgration in SQL Server

SQL-like DML and DDL statements

yes

APIs and other access methods

RESTful HTTP API

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

JDBC
ODBC
Thrift

CLI Client
JDBC
ODBC

JDBC
ODBC

Supported programming languages

Clojure
Java

C++
Java
PHP
Python

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

Transaction Functions

yes

via applications

yes

user defined functions and integration of map-reduce

user defined functions

Triggers

By using transaction functions

yes

via applications

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

none

But extensive use of caching in the application peers

Sharding

yes

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

But extensive use of caching in the application peers

selectable replication factor

yes

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
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

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

Can implement custom security layer via applications

Access rights for users, groups and roles

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

fine grained access rights according to SQL-standard

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.