DBMS > 4D vs. BigchainDB vs. Faircom DB vs. FileMaker vs. RocksDB

System Properties Comparison 4D vs. BigchainDB vs. Faircom DB vs. FileMaker vs. RocksDB

Editorial information provided by DB-Engines

Name

Description

Application development environment with integrated database management system

BigchainDB is scalable blockchain database offering decentralization, immutability and native assets

Native high-speed multi-model DBMS for relational and key-value store data simultaneously accessible through SQL and NoSQL APIs.

FileMaker is a cross-platform RDBMS that includes a GUI frontend.

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

Primary database model

Relational DBMS

Document store

Key-value store
Relational DBMS

Relational DBMS

Key-value store

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

Score	2.47
Rank	#110	Overall
	#54	Relational DBMS

Score	0.85
Rank	#208	Overall
	#35	Document stores

Score	0.29
Rank	#304	Overall
	#43	Key-value stores
	#136	Relational DBMS

Score	47.91
Rank	#20	Overall
	#14	Relational DBMS

Score	3.41
Rank	#86	Overall
	#11	Key-value stores

Website

www.4d.com

www.bigchaindb.com

www.faircom.com/products/faircom-db

www.claris.com/filemaker

rocksdb.org

Technical documentation

developer.4d.com

bigchaindb.readthedocs.io/en/latest

docs.faircom.com/docs/en/UUID-7446ae34-a1a7-c843-c894-d5322e395184.html

www.claris.com/resources/documentation

github.com/facebook/rocksdb/wiki

Developer

4D, Inc

FairCom Corporation

Claris

a subsidiary of Apple

Facebook, Inc.

Initial release

1984

2016

1979

1983

2013

Current release

v20, April 2023

V12, November 2020

19.4.1, November 2021

9.2.1, May 2024

License

Commercial or Open Source

commercial

Open Source

AGPL v3

commercial

Restricted, free version available

commercial

Open Source

BSD

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

Python

ANSI C, C++

C++

Server operating systems

OS X
Windows

Linux

AIX
FreeBSD
HP-UX
Linux
NetBSD
OS X
QNX
SCO
Solaris
VxWorks
Windows

easily portable to other OSs

iOS

client part only
Linux
OS X
Windows

Linux

Data scheme

yes

schema-free

schema free, schema optional, schema required, partial schema,

yes

schema-free

Typing

predefined data types such as float or date

yes

yes, ANSI SQL Types, JSON, typed binary structures

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

A http query request can return the data in XML format

Secondary indexes

yes

SQL

Support of SQL

yes

close to SQL 92

yes, ANSI SQL with proprietary extensions

yes

via plugins

APIs and other access methods

ODBC
RESTful HTTP API

by using 4D Mobile
SOAP webservices

CLI Client
RESTful HTTP API

ADO.NET
Direct SQL
JDBC
JPA
ODBC
RESTful HTTP/JSON API
RESTful MQTT/JSON API
RPC

Filemaker WebDirect
JDBC
ODBC

C++ API
Java API

Supported programming languages

4D proprietary IDE
PHP

Go
Haskell
Java
JavaScript
Python
Ruby

.Net
C
C#
C++
Java
JavaScript (Node.js and browser)
PHP
Python
Visual Basic

PHP

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

yes

.Net, JavaScript, C/C++

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

File partitioning, horizontal partitioning, sharding

Customizable business rules for table partitioning

none

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

selectable replication factor

yes, configurable to be parallel or serial, synchronous or asynchronous, uni-directional or bi-directional, ACID-consistent or eventually consistent (with custom conflict resolution).

Source-replica replication, warm standby

since Version 14

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency
Tunable consistency per server, database, table, and transaction

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

tunable from ACID to Eventually Consistent

yes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes,with MongoDB ord RethinkDB

Yes, tunable from durable to delayed durability to in-memory

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

User concepts

Access control

Users and groups

yes

Fine grained access rights according to SQL-standard with additional protections for files

simple rights management via user accounts and connection to external directory services

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.