DBMS > Drizzle vs. Riak TS vs. Sphinx vs. Yaacomo

System Properties Comparison Drizzle vs. Riak TS vs. Sphinx vs. Yaacomo

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.

Yaacomo seems to be discontinued and is removed from the DB-Engines ranking

Description

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

Riak TS is a distributed NoSQL database optimized for time series data and based on Riak KV

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

OpenCL based in-memory RDBMS, designed for efficiently utilizing the hardware via parallel computing

Primary database model

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

Score	0.28
Rank	#307	Overall
	#27	Time Series DBMS

Score	5.95
Rank	#55	Overall
	#5	Search engines

Website

sphinxsearch.com

yaacomo.com

Technical documentation

www.tiot.jp/riak-docs/riak/ts/latest

sphinxsearch.com/docs

Developer

Drizzle project, originally started by Brian Aker

Open Source, formerly Basho Technologies

Sphinx Technologies Inc.

Q2WEB GmbH

Initial release

2008

2015

2001

2009

Current release

7.2.4, September 2012

3.0.0, September 2022

3.5.1, February 2023

License

Commercial or Open Source

Open Source

GNU GPL

Open Source

GPL version 2, commercial licence available

commercial

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

Erlang

C++

Server operating systems

FreeBSD
Linux
OS X

Linux
OS X

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Android
Linux
Windows

Data scheme

yes

schema-free

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

restricted

yes

full-text index on all search fields

yes

SQL

Support of SQL

yes

with proprietary extensions

yes, limited

SQL-like query language (SphinxQL)

yes

APIs and other access methods

JDBC

HTTP API
Native Erlang Interface

Proprietary protocol

JDBC
ODBC

Supported programming languages

C
C++
Java
PHP

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

Server-side scripts

Stored procedures

Erlang

Triggers

hooks for callbacks inside the server can be used.

yes

pre-commit hooks and post-commit hooks

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

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

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

selectable replication factor

none

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

links between datasets can be stored

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.

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

Pluggable authentication mechanisms

e.g. LDAP, HTTP

fine grained access rights 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

New Basho Data Platform Provides Operational Simplicity for Enterprise Big Data Applications
7 June 2015, insideBIGDATA

Best open source databases for IoT applications
26 May 2017, Open Source For You

provided by Google News

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

5 Powerful Alternatives to Elasticsearch
25 April 2024, Insider Monkey

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

Royal Mail stamp prices could rise, warns Czech Sphinx
3 June 2024, Proactive Investors UK

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

provided by Google News

Share this page