DBMS > Datomic vs. EJDB vs. HEAVY.AI vs. Postgres-XL

System Properties Comparison Datomic vs. EJDB vs. HEAVY.AI vs. Postgres-XL

Please select another system to include it in the comparison.

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

Embeddable document-store database library with JSON representation of queries (in MongoDB style)

A high performance, column-oriented RDBMS, specifically developed to harness the massive parallelism of modern CPU and GPU hardware

Based on PostgreSQL enhanced with MPP and write-scale-out cluster features

Primary database model

Relational DBMS

Document store

Relational DBMS

Secondary database models

Spatial DBMS

Document store
Spatial DBMS

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

Score	1.59
Rank	#150	Overall
	#69	Relational DBMS

Score	0.27
Rank	#297	Overall
	#44	Document stores

Score	1.77
Rank	#141	Overall
	#65	Relational DBMS

Score	0.49
Rank	#256	Overall
	#117	Relational DBMS

Website

www.datomic.com

github.com/Softmotions/ejdb

github.com/heavyai/heavydb
www.heavy.ai

www.postgres-xl.org

Technical documentation

docs.datomic.com

github.com/Softmotions/ejdb/blob/master/README.md

docs.heavy.ai

www.postgres-xl.org/documentation

Developer

Cognitect

Softmotions

HEAVY.AI, Inc.

Initial release

2012

2016

2014

since 2012, originally named StormDB

Current release

1.0.6735, June 2023

5.10, January 2022

10 R1, October 2018

License

Commercial or Open Source

commercial

limited edition free

Open Source

GPLv2

Open Source

Apache Version 2; enterprise edition available

Open Source

Mozilla public license

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java, Clojure

C++ and CUDA

Server operating systems

All OS with a Java VM

server-less

Linux

Linux
macOS

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

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

XML type, but no XML query functionality

Secondary indexes

yes

SQL

Support of SQL

yes

distributed, parallel query execution

APIs and other access methods

RESTful HTTP API

in-process shared library

JDBC
ODBC
Thrift
Vega

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

Supported programming languages

Clojure
Java

Actionscript
C
C#
C++
Go
Java
JavaScript (Node.js)
Lua
Objective-C
Pike
Python
Ruby

All languages supporting JDBC/ODBC/Thrift
Python

.Net
C
C++
Delphi
Erlang
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

Server-side scripts

Stored procedures

yes

Transaction Functions

user defined functions

Triggers

By using transaction functions

yes

Partitioning methods

Methods for storing different data on different nodes

none

But extensive use of caching in the application peers

none

Sharding

Round robin

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

But extensive use of caching in the application peers

none

Multi-source replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

typically not needed, however similar functionality with collection joins possible

yes

Transaction concepts

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

ACID

MVCC

Concurrency

Support for concurrent manipulation of data

yes

Read/Write 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

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

Recent citations in the news

Stanchion Turns SQLite Into A Column Store
15 February 2024, iProgrammer

Nubank buys firm behind Clojure programming language
28 July 2020, Finextra

Zoona Case Study
16 December 2017, AWS Blog

Architecting Software for Leverage
13 November 2021, InfoQ.com

TerminusDB Takes on Data Collaboration with a git-Like Approach
1 December 2020, The New Stack

provided by Google News

Big Data Analytics: A Game Changer for Infrastructure
13 July 2023, Spiceworks News and Insights

HEAVY.AI Launches HEAVY 7.0, Introducing Real-Time Machine Learning Capabilities
19 April 2023, Business Wire

Making the most of geospatial intelligence
14 April 2023, InfoWorld

HEAVY.AI Partners with Bain, Maxar, and Nvidia to Provide Digital Twins for Telecom Networks
16 February 2023, Datanami

The insideBIGDATA IMPACT 50 List for Q4 2023
11 October 2023, insideBIGDATA

provided by Google News

Share this page