DBMS > 4D vs. RocksDB

System Properties Comparison 4D vs. RocksDB

Please select another system to include it in the comparison.

Our visitors often compare 4D and RocksDB with MySQL, Microsoft SQL Server and Oracle.

Editorial information provided by DB-Engines

Name

Description

Application development environment with integrated database management system

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

Primary database model

Relational DBMS

Key-value store

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

Score	2.74
Rank	#119	Overall
	#59	Relational DBMS

Score	4.47
Rank	#91	Overall
	#15	Key-value stores

Website

www.4d.com

rocksdb.org

Technical documentation

livedoc.4d.com

github.com/facebook/rocksdb/wiki

Developer

4D, Inc

Facebook, Inc.

Initial release

1984

2013

Current release

v18 R5, January 2021

7.9.2, December 2022

License

Commercial or Open Source

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

C++

Server operating systems

OS X
Windows

Linux

Data scheme

yes

schema-free

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

close to SQL 92

APIs and other access methods

ODBC
RESTful HTTP API

by using 4D Mobile
SOAP webservices

C++ API
Java API

Supported programming languages

4D proprietary IDE
PHP

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

none

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

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

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

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.