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

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

Editorial information provided by DB-Engines

Name

Description

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

Performant, highly scalable DBMS for AI and IoT applications

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

Relational DBMS

Key-value store
Vector DBMS

Relational DBMS

Time Series DBMS

Search engine

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

Score	0.96
Rank	#194	Overall
	#91	Relational DBMS

Score	0.00
Rank	#383	Overall
	#60	Key-value stores
	#13	Vector DBMS

Score	0.00
Rank	#383	Overall
	#158	Relational DBMS

Score	0.00
Rank	#383	Overall
	#41	Time Series DBMS

Score	5.98
Rank	#56	Overall
	#5	Search engines

Website

ignitetech.com/softwarelibrary/infobrightdb

Technical documentation

www.jaguardb.com/support.html

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

docs.siridb.com

sphinxsearch.com/docs

Developer

Ignite Technologies Inc.; formerly InfoBright Inc.

DataJaguar, Inc.

SADAS s.r.l.

Cesbit

Sphinx Technologies Inc.

Initial release

2005

2015

2006

2017

2001

Current release

3.3 July 2023

8.0

3.5.1, February 2023

License

Commercial or Open Source

commercial

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

Open Source

GPL V3.0

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.

Implementation language

C++

the server part. Clients available in other languages

C++

Server operating systems

Linux
Windows

Linux

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.

Secondary indexes

Knowledge Grid Technology used instead

yes

full-text index on all search fields

SQL

Support of SQL

yes

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

yes

SQL-like query language (SphinxQL)

APIs and other access methods

ADO.NET
JDBC
ODBC

JDBC
ODBC

JDBC
ODBC
Proprietary protocol

HTTP API

Proprietary protocol

Supported programming languages

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

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

.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

Triggers

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

horizontal partitioning

Sharding

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

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Multi-source replication

none

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

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'

yes

User concepts

Access control

fine grained access rights according to SQL-standard

exploiting MySQL or PostgreSQL frontend capabilities

rights management via user accounts

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.

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

SiriDB tijdreeks database analyseert time series data vanuit elke bron
22 January 2017, Dutch IT Channel

provided by Google 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 Googles 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

Share this page