DBMS > MySQL vs. searchxml vs. SpaceTime vs. Sphinx vs. VictoriaMetrics

System Properties Comparison MySQL vs. searchxml vs. SpaceTime vs. Sphinx vs. VictoriaMetrics

Editorial information provided by DB-Engines

Name

Description

Widely used open source RDBMS

DBMS for structured and unstructured content wrapped with an application server

SpaceTime is a spatio-temporal DBMS with a focus on performance.

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

A fast, cost-effective and scalable Time Series DBMS and monitoring solution

Primary database model

Relational DBMS

Key/Value like access via memcached API

Native XML DBMS
Search engine

Spatial DBMS

Search engine

Time Series DBMS

Secondary database models

Document store
Spatial DBMS

Relational DBMS

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

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Score	0.00
Rank	#385	Overall
	#7	Native XML DBMS
	#24	Search engines

Score	0.00
Rank	#385	Overall
	#7	Spatial DBMS

Score	5.97
Rank	#56	Overall
	#5	Search engines

Score	1.23
Rank	#165	Overall
	#15	Time Series DBMS

Website

www.mysql.com

www.searchxml.net/category/products

www.mireo.com/spacetime

sphinxsearch.com

victoriametrics.com

Technical documentation

dev.mysql.com/doc

www.searchxml.net/support/handouts

sphinxsearch.com/docs

docs.victoriametrics.com
github.com/VictoriaMetrics/VictoriaMetrics/wiki

Developer

Oracle

since 2010, originally MySQL AB, then Sun

informationpartners gmbh

Mireo

Sphinx Technologies Inc.

VictoriaMetrics

Initial release

1995

2015

2020

2001

2018

Current release

9.0.0, July 2024

1.0

3.5.1, February 2023

v1.91, May 2023

License

Commercial or Open Source

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

commercial

Open Source

GPL version 2, commercial licence available

Open Source

Apache 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 and C++

C++

Server operating systems

FreeBSD
Linux
OS X
Solaris
Windows

Windows

Linux

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

FreeBSD
Linux
macOS
OpenBSD

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.

yes

Secondary indexes

yes

full-text index on all search fields

SQL

Support of SQL

yes

with proprietary extensions

A subset of ANSI SQL is implemented

SQL-like query language (SphinxQL)

APIs and other access methods

ADO.NET
JDBC
ODBC
Proprietary native API

RESTful HTTP API
WebDAV
XQuery
XSLT

RESTful HTTP API

Proprietary protocol

Graphite protocol
InfluxDB Line Protocol
OpenTSDB
Prometheus Query API
Prometheus Remote Read/Write

Supported programming languages

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

C++

most other programming languages supported via APIs

C#
C++
Python

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

Server-side scripts

Stored procedures

yes

proprietary syntax

yes

on the application server

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

none

Fixed-grid hypercubes

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

yes

sychronisation to multiple collections

Real-time block device replication (DRBD)

none

Synchronous 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

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

multiple readers, single writer

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 with fine-grained authorization concept

no user groups or roles

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

yes

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.