DBMS > 4D vs. Firebolt vs. MySQL vs. SingleStore vs. Tkrzw

System Properties Comparison 4D vs. Firebolt vs. MySQL vs. SingleStore vs. Tkrzw

Editorial information provided by DB-Engines

Name

Description

Application development environment with integrated database management system

Highly scalable cloud data warehouse and analytics product

Forked from Clickhouse

Widely used open source RDBMS

MySQL wire-compliant distributed RDBMS that combines an in-memory row-oriented and a disc-based column-oriented storage with patented universal storage to handle transactional and analytical workloads in one single table type

A concept of libraries, allowing an application program to store and query key-value pairs in a file. Successor of Tokyo Cabinet and Kyoto Cabinet

Primary database model

Relational DBMS

Key/Value like access via memcached API

Relational DBMS

Key-value store

Secondary database models

Document store
Spatial DBMS

Document store
Spatial DBMS
Time Series DBMS
Vector DBMS

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

Score	2.37
Rank	#110	Overall
	#54	Relational DBMS

Score	1.49
Rank	#148	Overall
	#68	Relational DBMS

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Score	4.02
Rank	#74	Overall
	#39	Relational DBMS

Score	0.00
Rank	#385	Overall
	#61	Key-value stores

Website

Technical documentation

Developer

4D, Inc

Firebolt Analytics Inc.

Oracle

since 2010, originally MySQL AB, then Sun

SingleStore Inc.

Mikio Hirabayashi

Initial release

1984

2020

1995

2013

2020

Current release

v20, April 2023

9.0.0, July 2024

8.5, January 2024

0.9.3, August 2020

License

Commercial or Open Source

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

commercial

free developer edition available

Open Source

Apache Version 2.0

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

C and C++

C++, Go

C++

Server operating systems

OS X
Windows

hosted

FreeBSD
Linux
OS X
Solaris
Windows

Linux

64 bit version required

Linux
macOS

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

yes

with proprietary extensions

yes

but no triggers and foreign keys

APIs and other access methods

ODBC
RESTful HTTP API

by using 4D Mobile
SOAP webservices

.Net
ODBC
RESTful HTTP API

ADO.NET
JDBC
ODBC
Proprietary native API

Cluster Management API

as HTTP Rest and CLI
HTTP API
JDBC
MongoDB API
ODBC

Supported programming languages

4D proprietary IDE
PHP

Go
JavaScript (Node.js)
Python

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Bash
C
C#
Java
JavaScript (Node.js)
Python

C++
Java
Python
Ruby

Server-side scripts

Stored procedures

yes

proprietary syntax

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

hash partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

depending on storage layer

Multi-source replication
Source-replica replication

Source-replica replication

stores two copies of each physical data partition on two separate nodes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

can define user-defined aggregate functions for map-reduce-style calculations

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

not for MyISAM storage engine

ACID

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

yes, multi-version concurrency control (MVCC)

yes

Durability

Support for making data persistent

yes

All updates are persistent, including those to disk-based columnstores and memory-based row stores. Transaction commits are supported via write-ahead log.

yes

In-memory capabilities

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

yes

using specific database classes

User concepts

Access control

Users and groups

Users with fine-grained authorization concept

no user groups or roles

Fine grained access control via users, groups and roles

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.