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

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

Editorial information provided by DB-Engines

Name

Description

Performant, highly scalable DBMS for AI and IoT applications

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

Cloud-based data warehousing service for structured and semi-structured data

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

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
	#158	Relational DBMS

Score	121.33
Rank	#9	Overall
	#6	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

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

docs.snowflake.net/manuals/index.html

sphinxsearch.com/docs

Developer

DataJaguar, Inc.

SADAS s.r.l.

Snowflake Computing Inc.

Sphinx Technologies Inc.

STS Soft SC

Initial release

2015

2006

2014

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

commercial

free trial version available

commercial

Open Source

GPL version 2, commercial licence available

Open Source

GPLv2, commercial license available

Cloud-based only

Only available as a cloud service

yes

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

AIX
Linux
Windows

hosted

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Windows

Data scheme

yes

support of semi-structured data formats (JSON, XML, Avro)

yes

Typing

predefined data types such as float or date

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.

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

SQL-like query language (SphinxQL)

APIs and other access methods

JDBC
ODBC

JDBC
ODBC
Proprietary protocol

CLI Client
JDBC
ODBC

Proprietary protocol

.NET Client API

Supported programming languages

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

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

JavaScript (Node.js)
Python

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

C#
Java

Server-side scripts

Stored procedures

user defined functions

Triggers

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

yes

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

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

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.

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

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

Users with fine-grained authorization concept, user roles and pluggable authentication

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.