DBMS > Drizzle vs. Infobright vs. Sadas Engine vs. Sphinx

System Properties Comparison Drizzle vs. Infobright vs. Sadas Engine vs. Sphinx

Please select another system to include it in the comparison.

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

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

High performant column-oriented DBMS for analytic workloads using MySQL or PostgreSQL as a frontend

SADAS Engine is a columnar DBMS specifically designed for high performance in data warehouse environments

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

Primary database model

Relational DBMS

Search engine

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

Score	1.00
Rank	#193	Overall
	#90	Relational DBMS

Score	0.03
Rank	#379	Overall
	#156	Relational DBMS

Score	6.03
Rank	#60	Overall
	#6	Search engines

Website

ignitetech.com/softwarelibrary/infobrightdb

www.sadasengine.com

sphinxsearch.com

Technical documentation

www.sadasengine.com/en/sadas-engine-download-free-trial-and-documentation/#documentation

sphinxsearch.com/docs

Developer

Drizzle project, originally started by Brian Aker

Ignite Technologies Inc.; formerly InfoBright Inc.

SADAS s.r.l.

Sphinx Technologies Inc.

Initial release

2008

2005

2006

2001

Current release

7.2.4, September 2012

8.0

3.5.1, February 2023

License

Commercial or Open Source

Open Source

GNU GPL

commercial

The open source (GPLv2) version did not support inserts/updates/deletes and was discontinued with July 2016

commercial

free trial version available

Open Source

GPL version 2, commercial licence 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

FreeBSD
Linux
OS X

Linux
Windows

AIX
Linux
Windows

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Data scheme

yes

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.

Secondary indexes

yes

Knowledge Grid Technology used instead

yes

full-text index on all search fields

SQL

Support of SQL

yes

with proprietary extensions

yes

SQL-like query language (SphinxQL)

APIs and other access methods

JDBC

ADO.NET
JDBC
ODBC

JDBC
ODBC
Proprietary protocol

Proprietary protocol

Supported programming languages

C
C++
Java
PHP

.Net
C
C#
C++
D
Eiffel
Erlang
Haskell
Java
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

.Net
C
C#
C++
Groovy
Java
PHP
Python

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

Server-side scripts

Stored procedures

Triggers

hooks for callbacks inside the server can be used.

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

horizontal partitioning

Sharding

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

Replication methods

Methods for redundantly storing data on multiple nodes

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

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

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

In-memory capabilities

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

yes

managed by 'Learn by Usage'

User concepts

Access control

Pluggable authentication mechanisms

e.g. LDAP, HTTP

fine grained access rights according to SQL-standard

exploiting MySQL or PostgreSQL frontend capabilities

Access rights for users, groups and roles according to SQL-standard

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

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

Beyond the Concert Hall: 5 Organizations Making a Difference in Classical Music in 2018 | WQXR Editorial
22 December 2018, WQXR Radio

provided by Google News

Share this page