DBMS > DataFS vs. Datomic vs. Firebird vs. RocksDB vs. SAP SQL Anywhere

System Properties Comparison DataFS vs. Datomic vs. Firebird vs. RocksDB vs. SAP SQL Anywhere

Editorial information provided by DB-Engines

Name

Description

All data is stored inside objects which are linked by so-called link attributes. Objects consist of classes which can be extended and de-extended at runtime. Graphs can be defined with a struct.

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

Firebird is an open source RDBMS forked from Borland's InterBase

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

RDBMS database and synchronization technologies for server, desktop, remote office, and mobile environments

Primary database model

Secondary database models

Graph DBMS

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

Score	0.06
Rank	#354	Overall
	#15	Object oriented DBMS

Score	1.59
Rank	#150	Overall
	#69	Relational DBMS

Score	20.82
Rank	#30	Overall
	#18	Relational DBMS

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Score	4.25
Rank	#79	Overall
	#43	Relational DBMS

Website

www.sap.com/products/technology-platform/sql-anywhere.html

Technical documentation

dev.mobiland.com/Overview.xsp

docs.datomic.com

www.firebirdsql.org/en/reference-manuals

github.com/facebook/rocksdb/wiki

help.sap.com/docs/SAP_SQL_Anywhere

Developer

Mobiland AG

Cognitect

Firebird Foundation

Facebook, Inc.

SAP

formerly Sybase

Initial release

2018

2012

2000

As fork of Borland's InterBase

2013

1992

Current release

1.1.263, October 2022

1.0.6735, June 2023

5.0.0, January 2024

8.11.4, April 2024

17, July 2015

License

Commercial or Open Source

commercial

limited edition free

Open Source

Initial Developer's Public License

Open Source

BSD

commercial

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

C++

Server operating systems

Windows

All OS with a Java VM

AIX
FreeBSD
HP-UX
Linux
OS X
server-less

Firebird Embedded Server
Solaris
Unix
Windows

Linux

AIX
HP-UX
Linux
OS X
Solaris
Windows

Data scheme

Classes, Structs, and Lists are written in proprietary DataTypeDefinitionLanguage (.dtdl) and Objects consisting of those are written in proprietary DataAccessDefinitionLanguage (.dadl)

yes

schema-free

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

yes

APIs and other access methods

.NET Client API
Proprietary client DLL
WinRT client

RESTful HTTP API

ADO.NET
C/C++ API
JDBC

Jaybird
ODBC
OLE DB

C++ API
Java API

ADO.NET
HTTP API
JDBC
ODBC

Supported programming languages

.Net
C
C#
C++
VB.Net

Clojure
Java

C
C#
C++
Delphi
Java
JavaScript

Node.js
Lua
Perl
PHP
Python
Ruby

C
C++
Go
Java
Perl
Python
Ruby

C
C#
C++
Delphi
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

Server-side scripts

Stored procedures

yes

Transaction Functions

PSQL

yes, in C/C++, Java, .Net or Perl

Triggers

no, except callback-events from server when changes happened

By using transaction functions

yes

Partitioning methods

Methods for storing different data on different nodes

Proprietary Sharding system

none

But extensive use of caching in the application peers

none

horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

But extensive use of caching in the application peers

Source-replica replication

yes

Source-replica replication

Database mirroring

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

yes

Transaction concepts

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

ACID

yes

ACID

Concurrency

Support for concurrent manipulation of data

yes

Features a multi-generational MVCC architecture, readers do not block writers

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

Windows-Profile

Users with fine-grained authorization concept

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.