DBMS > SAP HANA vs. Sphinx vs. SwayDB vs. ToroDB

System Properties Comparison SAP HANA vs. Sphinx vs. SwayDB vs. ToroDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

ToroDB seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

In-memory, column based data store. Available as appliance or cloud service

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

An embeddable, non-blocking, type-safe key-value store for single or multiple disks and in-memory storage

A MongoDB-compatible JSON document store, built on top of PostgreSQL

Primary database model

Secondary database models

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	41.32
Rank	#23	Overall
	#16	Relational DBMS

Score	5.97
Rank	#56	Overall
	#5	Search engines

Score	0.00
Rank	#384	Overall
	#60	Key-value stores

Website

www.sap.com/products/hana.html

sphinxsearch.com

swaydb.simer.au

github.com/torodb/server

Technical documentation

help.sap.com/hana

sphinxsearch.com/docs

Developer

SAP

Sphinx Technologies Inc.

Simer Plaha

8Kdata

Initial release

2010

2001

2018

2016

Current release

2.0 SPS07 (April 4, 2023), April 2023

3.5.1, February 2023

License

Commercial or Open Source

commercial

Open Source

GPL version 2, commercial licence available

Open Source

GNU Affero GPL V3.0

Open Source

AGPL-V3

Cloud-based only

Only available as a cloud service

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

C++

Scala

Java

Server operating systems

Appliance or cloud-service

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

All OS with a Java 7 VM

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

string, integer, double, boolean, date, object_id

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

yes

full-text index on all search fields

SQL

Support of SQL

yes

SQL-like query language (SphinxQL)

APIs and other access methods

JDBC
ODBC

Proprietary protocol

Supported programming languages

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

Java
Kotlin
Scala

Server-side scripts

Stored procedures

SQLScript, R

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

yes

Sharding

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

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

Source-replica replication

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

Atomic execution of operations

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

User concepts

Access control

yes

Access rights for users and roles

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.