DBMS > JaguarDB vs. OrigoDB vs. Sadas Engine vs. Sphinx vs. STSdb

System Properties Comparison JaguarDB vs. OrigoDB vs. Sadas Engine vs. Sphinx vs. STSdb

Editorial information provided by DB-Engines

Name

Description

Performant, highly scalable DBMS for AI and IoT applications

A fully ACID in-memory object graph database

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

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

Key-Value Store with special method for indexing

optimized for high performance using a special indexing method

Primary database model

Key-value store
Vector DBMS

Document store
Object oriented DBMS

Relational DBMS

Search engine

Key-value store

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

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

Score	0.00
Rank	#383	Overall
	#53	Document stores
	#20	Object oriented DBMS

Score	0.00
Rank	#383	Overall
	#158	Relational DBMS

Score	5.98
Rank	#56	Overall
	#5	Search engines

Score	0.04
Rank	#360	Overall
	#52	Key-value stores

Website

github.com/STSSoft/STSdb4

Technical documentation

www.jaguardb.com/support.html

origodb.com/docs

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

sphinxsearch.com/docs

Developer

DataJaguar, Inc.

Robert Friberg et al

SADAS s.r.l.

Sphinx Technologies Inc.

STS Soft SC

Initial release

2015

2009

under the name LiveDB

2006

2001

2011

Current release

3.3 July 2023

8.0

3.5.1, February 2023

4.0.8, September 2015

License

Commercial or Open Source

Open Source

GPL V3.0

Open Source

commercial

free trial version available

Open Source

GPL version 2, commercial licence available

Open Source

GPLv2, commercial license 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

Linux
Windows

AIX
Linux
Windows

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Windows

Data scheme

yes

Typing

predefined data types such as float or date

yes

User defined using .NET types and collections

yes

primitive types and user defined types (classes)

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.

can be achieved using .NET

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

SQL-like query language (SphinxQL)

APIs and other access methods

JDBC
ODBC

.NET Client API
HTTP API
LINQ

JDBC
ODBC
Proprietary protocol

Proprietary protocol

.NET Client API

Supported programming languages

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

.Net

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

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

C#
Java

Server-side scripts

Stored procedures

yes

Triggers

yes

Domain Events

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

client side managed; servers are not synchronized

horizontal partitioning

Sharding

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

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

Source-replica replication

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

depending on model

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

Write ahead log

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

managed by 'Learn by Usage'

User concepts

Access control

rights management via user accounts

Role based authorization

Access rights for users, groups and roles 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

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

Beyond the Concert Hall: 5 Organizations Making a Difference in Classical Music in 2018 | WQXR Editorial
22 December 2018, WQXR Radio

provided by Google News

Share this page