DBMS > 4D vs. Drizzle vs. MySQL vs. Sphinx vs. ToroDB

System Properties Comparison 4D vs. Drizzle vs. MySQL vs. Sphinx vs. ToroDB

Editorial information provided by DB-Engines

Name

Drizzle has published its last release in September 2012. The open-source project is discontinued and Drizzle is excluded from the DB-Engines ranking.

ToroDB seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

Application development environment with integrated database management system

MySQL fork with a pluggable micro-kernel and with an emphasis of performance over compatibility.

Widely used open source RDBMS

Open source search engine for searching in data from different sources, e.g. relational databases

A MongoDB-compatible JSON document store, built on top of PostgreSQL

Primary database model

Relational DBMS

Key/Value like access via memcached API

Search engine

Document store

Secondary database models

Document store
Spatial DBMS

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

Score	2.37
Rank	#110	Overall
	#54	Relational DBMS

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Score	5.97
Rank	#56	Overall
	#5	Search engines

Website

www.4d.com

www.mysql.com

sphinxsearch.com

github.com/torodb/server

Technical documentation

developer.4d.com

dev.mysql.com/doc

sphinxsearch.com/docs

Developer

4D, Inc

Drizzle project, originally started by Brian Aker

Oracle

since 2010, originally MySQL AB, then Sun

Sphinx Technologies Inc.

8Kdata

Initial release

1984

2008

1995

2001

2016

Current release

v20, April 2023

7.2.4, September 2012

9.0.0, July 2024

3.5.1, February 2023

License

Commercial or Open Source

commercial

Open Source

GNU GPL

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

GPL version 2, commercial licence available

Open Source

AGPL-V3

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

C and C++

C++

Java

Server operating systems

OS X
Windows

FreeBSD
Linux
OS X

FreeBSD
Linux
OS X
Solaris
Windows

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

All OS with a Java 7 VM

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

string, integer, double, boolean, date, object_id

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

full-text index on all search fields

SQL

Support of SQL

yes

close to SQL 92

yes

with proprietary extensions

yes

with proprietary extensions

SQL-like query language (SphinxQL)

APIs and other access methods

ODBC
RESTful HTTP API

by using 4D Mobile
SOAP webservices

JDBC

ADO.NET
JDBC
ODBC
Proprietary native API

Proprietary protocol

Supported programming languages

4D proprietary IDE
PHP

C
C++
Java
PHP

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

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

Server-side scripts

Stored procedures

yes

proprietary syntax

Triggers

yes

hooks for callbacks inside the server can be used.

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

Partitioning is done manually, search queries against distributed index is supported

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

Multi-source replication
Source-replica replication

none

Source-replica replication

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

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

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

yes

Durability

Support for making data persistent

yes

The original contents of fields are not stored in the Sphinx index.

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

Pluggable authentication mechanisms

e.g. LDAP, HTTP

Users with fine-grained authorization concept

no user groups or roles

Access rights for users 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.