DBMS > JaguarDB vs. MySQL vs. Sadas Engine vs. SiriDB vs. Sphinx

System Properties Comparison JaguarDB vs. MySQL vs. Sadas Engine vs. SiriDB vs. Sphinx

Editorial information provided by DB-Engines

Name

Description

Performant, highly scalable DBMS for AI and IoT applications

Widely used open source RDBMS

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

Open Source Time Series DBMS

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

Primary database model

Key-value store
Vector DBMS

Relational DBMS

Key/Value like access via memcached API

Relational DBMS

Time Series DBMS

Search engine

Secondary database models

Document store
Spatial DBMS

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

Score	0.09
Rank	#356	Overall
	#53	Key-value stores
	#13	Vector DBMS

Score	1087.72
Rank	#2	Overall
	#2	Relational DBMS

Score	0.03
Rank	#379	Overall
	#156	Relational DBMS

Score	0.11
Rank	#346	Overall
	#32	Time Series DBMS

Score	6.03
Rank	#60	Overall
	#6	Search engines

Website

Technical documentation

www.jaguardb.com/support.html

dev.mysql.com/doc

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

docs.siridb.com

sphinxsearch.com/docs

Developer

DataJaguar, Inc.

Oracle

since 2010, originally MySQL AB, then Sun

SADAS s.r.l.

Cesbit

Sphinx Technologies Inc.

Initial release

2015

1995

2006

2017

2001

Current release

3.3 July 2023

8.3.0, January 2024

8.0

3.5.1, February 2023

License

Commercial or Open Source

Open Source

GPL V3.0

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

commercial

free trial version available

Open Source

MIT License

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.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

C++

the server part. Clients available in other languages

C and C++

C++

Server operating systems

Linux

FreeBSD
Linux
OS X
Solaris
Windows

AIX
Linux
Windows

Linux

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Data scheme

yes

Typing

predefined data types such as float or date

yes

Numeric data

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

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

yes

with proprietary extensions

yes

SQL-like query language (SphinxQL)

APIs and other access methods

JDBC
ODBC

ADO.NET
JDBC
ODBC
Proprietary native API

JDBC
ODBC
Proprietary protocol

HTTP API

Proprietary protocol

Supported programming languages

C
C++
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby
Scala

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

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

C
C++
Go
Java
JavaScript (Node.js)
PHP
Python
R

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

Server-side scripts

Stored procedures

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

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

Multi-source replication
Source-replica replication

none

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

Transaction concepts

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

ACID

not for MyISAM storage engine

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.

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'

yes

User concepts

Access control

rights management via user accounts

Users with fine-grained authorization concept

no user groups or roles

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

simple rights management via user accounts

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.