DBMS > searchxml vs. Sphinx vs. VoltDB vs. YTsaurus

System Properties Comparison searchxml vs. Sphinx vs. VoltDB vs. YTsaurus

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

DBMS for structured and unstructured content wrapped with an application server

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

Distributed In-Memory NewSQL RDBMS

Used for OLTP applications with a high frequency of relatively simple transactions, that can hold all their data in memory

YTsaurus is an open source platform for distributed storage and processing.

Primary database model

Native XML DBMS
Search engine

Search engine

Relational DBMS

Document store
Key-value store

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

Score	0.03
Rank	#390	Overall
	#7	Native XML DBMS
	#24	Search engines

Score	5.95
Rank	#55	Overall
	#5	Search engines

Score	1.47
Rank	#157	Overall
	#73	Relational DBMS

Score	0.21
Rank	#324	Overall
	#45	Document stores
	#48	Key-value stores

Website

www.searchxml.net/category/products

sphinxsearch.com

www.voltdb.com

ytsaurus.tech

Technical documentation

www.searchxml.net/support/handouts

sphinxsearch.com/docs

docs.voltdb.com

ytsaurus.tech/docs/en

Developer

informationpartners gmbh

Sphinx Technologies Inc.

VoltDB Inc.

Yandex

Initial release

2015

2001

2010

2023

Current release

1.0

3.5.1, February 2023

11.3, April 2022

License

Commercial or Open Source

commercial

Open Source

GPL version 2, commercial licence available

Open Source

AGPL for Community Edition, commercial license for Enterprise, AWS, and Pro Editions

Open Source

Apache License, Version 2.0

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

Java, C++

C++

Server operating systems

Windows

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Linux
OS X

for development

Ubuntu

Data scheme

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.

yes

Secondary indexes

yes

full-text index on all search fields

yes

SQL

Support of SQL

SQL-like query language (SphinxQL)

yes

only a subset of SQL 99

YQL, an SQL-based language, is supported

APIs and other access methods

RESTful HTTP API
WebDAV
XQuery
XSLT

Proprietary protocol

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

C++

most other programming languages supported via APIs

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

C++
Go
Java
JavaScript
Python

Server-side scripts

Stored procedures

yes

on the application server

Java

Triggers

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

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

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

sychronisation to multiple collections

none

Multi-source replication
Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

FOREIGN KEY constraints are not supported

Transaction concepts

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

multiple readers, single writer

ACID

Transactions are executed single-threaded within stored procedures

ACID

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

yes

Durability

Support for making data persistent

yes

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

yes

Snapshots and command logging

yes

In-memory capabilities

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

User concepts

Access control

Domain, group and role-based access control at the document level and for application services

Users and roles with access to stored procedures

Access Control Lists

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

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 Google's 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

Unveiling Volt Active Data's game-changing approach to limitless app performance
16 October 2023, YourStory

VoltDB Launches Active(N) Lossless Cross Data Center Replication
31 August 2021, PR Newswire

VoltDB Turns to Real-Time Analytics with NewSQL Database
30 January 2014, Datanami

VoltDB Upgrades Power, Security of Its In-Memory Database
1 February 2017, eWeek

VoltDB Adds Geospatial Support, Cross-Site Replication
28 January 2016, The New Stack

provided by Google News

Share this page