DBMS > 4D vs. Drizzle vs. OrigoDB vs. Sphinx vs. TerarkDB

System Properties Comparison 4D vs. Drizzle vs. OrigoDB vs. Sphinx vs. TerarkDB

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.

Description

Application development environment with integrated database management system

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

A fully ACID in-memory object graph database

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

A key-value store forked from RocksDB with advanced compression algorithms. It can be used standalone or as a storage engine for MySQL and MongoDB

Primary database model

Relational DBMS

Document store
Object oriented DBMS

Search engine

Key-value store

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

Score	2.58
Rank	#108	Overall
	#54	Relational DBMS

Score	0.00
Rank	#383	Overall
	#53	Document stores
	#20	Object oriented DBMS

Score	5.98
Rank	#56	Overall
	#5	Search engines

Score	0.00
Rank	#383	Overall
	#60	Key-value stores

Website

www.4d.com

origodb.com

sphinxsearch.com

github.com/bytedance/terarkdb

Technical documentation

developer.4d.com

origodb.com/docs

sphinxsearch.com/docs

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

Developer

4D, Inc

Drizzle project, originally started by Brian Aker

Robert Friberg et al

Sphinx Technologies Inc.

ByteDance, originally Terark

Initial release

1984

2008

2009

under the name LiveDB

2001

2016

Current release

v20, April 2023

7.2.4, September 2012

3.5.1, February 2023

License

Commercial or Open Source

commercial

Open Source

GNU GPL

Open Source

GPL version 2, commercial licence available

commercial

restricted open source version available

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

FreeBSD
Linux
OS X

Linux
Windows

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

User defined using .NET types and collections

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

can be achieved using .NET

Secondary indexes

yes

full-text index on all search fields

SQL

Support of SQL

yes

close to SQL 92

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

.NET Client API
HTTP API
LINQ

Proprietary protocol

C++ API
Java API

Supported programming languages

4D proprietary IDE
PHP

C
C++
Java
PHP

.Net

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

C++
Java

Server-side scripts

Stored procedures

yes

Triggers

yes

hooks for callbacks inside the server can be used.

yes

Domain Events

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

horizontal partitioning

client side managed; servers are not synchronized

Sharding

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

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

Multi-source replication
Source-replica replication

Source-replica 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

depending on model

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Write ahead log

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

Role based authorization

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

MySQL, PostgreSQL and Redis are the winners of the March ranking
2 March 2016, Paul Andlinger

show all

MySQL won the April ranking; did its forks follow?
1 April 2015, Paul Andlinger

Has MySQL finally lost its mojo?
1 July 2013, Matthias Gelbmann

show all

The DB-Engines ranking includes now search engines
4 February 2013, Paul Andlinger

show all

Recent citations in the news

Switching From Sphinx to MkDocs Documentation — What Did I Gain and Lose
2 February 2024, Towards Data Science

Manticore is a Faster Alternative to Elasticsearch in C++
25 July 2022, hackernoon.com

Perplexity AI: From Its Use To Operation, Everything You Need To Know About Googles Newest Challenger
11 January 2024, Free Press Journal

The Pirate Bay was recently down for over a week due to a DDoS attack
29 October 2019, The Hacker News

How to Build 600+ Links in One Month
4 September 2020, Search Engine Journal

provided by Google News

A Chinese company is making the cloud 200x faster · TechNode
3 July 2017, TechNode

provided by Google News

Share this page