DBMS > Datomic vs. FatDB vs. IBM Db2 vs. OpenEdge vs. SQLite

System Properties Comparison Datomic vs. FatDB vs. IBM Db2 vs. OpenEdge vs. SQLite

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.

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.

Common in IBM host environments, 2 different versions for host and Windows/Linux

Application development environment with integrated database management system

Widely used embeddable, in-process RDBMS

Primary database model

Relational DBMS

Document store
Key-value store

Relational DBMS

Since Version 10.5 support for JSON/BSON documents compatible with MongoDB

Relational DBMS

Secondary database models

Document store
RDF store

in Db2 LUW (Linux, Unix, Windows)
Spatial DBMS

with Db2 Spatial Extender

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

Score	1.59
Rank	#150	Overall
	#69	Relational DBMS

Score	128.46
Rank	#8	Overall
	#5	Relational DBMS

Score	3.51
Rank	#86	Overall
	#46	Relational DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

www.datomic.com

www.ibm.com/products/db2

www.progress.com/openedge

www.sqlite.org

Technical documentation

docs.datomic.com

www.ibm.com/docs/en/db2

documentation.progress.com/output/ua/OpenEdge_latest

www.sqlite.org/docs.html

Developer

Cognitect

FatCloud

IBM

Progress Software Corporation

Dwayne Richard Hipp

Initial release

2012

1983

host version

1984

2000

Current release

1.0.6735, June 2023

12.1, October 2016

OpenEdge 12.2, March 2020

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

commercial

limited edition free

commercial

free version is available

commercial

Open Source

Public Domain

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 C++

Server operating systems

All OS with a Java VM

Windows

AIX
HP-UX
Linux
Solaris
Windows
z/OS

AIX
HP-UX
Linux
Solaris
Windows

server-less

Data scheme

yes

schema-free

yes

dynamic column types

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

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

yes

close to SQL 92

yes

SQL-92 is not fully supported

APIs and other access methods

RESTful HTTP API

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

ADO.NET
JDBC
JSON style queries

MongoDB compatible
ODBC
XQuery

JDBC
ODBC

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

Clojure
Java

C
C#
C++
Cobol
Delphi
Fortran
Java
Perl
PHP
Python
Ruby
Visual Basic

Progress proprietary ABL (Advanced Business Language)

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Server-side scripts

Stored procedures

yes

Transaction Functions

yes

via applications

yes

Triggers

By using transaction functions

yes

via applications

yes

Partitioning methods

Methods for storing different data on different nodes

none

But extensive use of caching in the application peers

Sharding

only with Windows/Unix/Linux Version

horizontal partitioning

since Version 11.4

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

But extensive use of caching in the application peers

selectable replication factor

yes

with separate tools (MQ, InfoSphere)

Source-replica replication

none

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

via file-system locks

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

fine grained access rights according to SQL-standard

Users and groups

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.