DBMS > RavenDB vs. Sadas Engine vs. Snowflake vs. Sphinx

System Properties Comparison RavenDB vs. Sadas Engine vs. Snowflake vs. Sphinx

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Open Source Operational and Transactional Enterprise NoSQL Document Database

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

Primary database model

Document store

Relational DBMS

Search engine

Secondary database models

Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	2.68
Rank	#102	Overall
	#19	Document stores

Score	0.00
Rank	#385	Overall
	#159	Relational DBMS

Score	133.72
Rank	#7	Overall
	#5	Relational DBMS

Score	5.97
Rank	#56	Overall
	#5	Search engines

Website

Technical documentation

ravendb.net/docs

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

docs.snowflake.net/manuals/index.html

sphinxsearch.com/docs

Developer

Hibernating Rhinos

SADAS s.r.l.

Snowflake Computing Inc.

Sphinx Technologies Inc.

Initial release

2010

2006

2014

2001

Current release

5.4, July 2022

8.0

3.5.1, February 2023

License

Commercial or Open Source

Open Source

AGPL version 3, commercial license available

commercial

free trial version available

commercial

Open Source

GPL version 2, commercial licence 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++

Server operating systems

Linux
macOS
Raspberry Pi
Windows

AIX
Linux
Windows

hosted

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Data scheme

schema-free

yes

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

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

SQL-like query language (RQL)

yes

SQL-like query language (SphinxQL)

APIs and other access methods

.NET Client API
F# Client API
Go Client API
Java Client API
NodeJS Client API
PHP Client API
Python Client API
RESTful HTTP API

JDBC
ODBC
Proprietary protocol

CLI Client
JDBC
ODBC

Proprietary protocol

Supported programming languages

.Net
C#
F#
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

.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

Server-side scripts

Stored procedures

yes

user defined functions

Triggers

yes

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

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

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Default ACID transactions on the local node (eventually consistent across the cluster). Atomic operations with cluster-wide ACID transactions. Eventual consistency for indexes and full-text search indexes.

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID, Cluster-wide transaction available

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'

User concepts

Access control

Authorization levels configured per client per database

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.