DBMS > SAP HANA vs. Sphinx vs. SWC-DB vs. Transwarp KunDB

System Properties Comparison SAP HANA vs. Sphinx vs. SWC-DB vs. Transwarp KunDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

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

A high performance, scalable Wide Column DBMS

OLTP DBMS based on a distributed architecture and highly compatible with MySQL and Oracle

Primary database model

Secondary database models

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

Time Series DBMS

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

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Score	5.98
Rank	#56	Overall
	#5	Search engines

Score	0.01
Rank	#376	Overall
	#13	Wide column stores

Score	0.10
Rank	#344	Overall
	#151	Relational DBMS

Website

www.sap.com/products/hana.html

sphinxsearch.com

github.com/kashirin-alex/swc-db
www.swcdb.org

www.transwarp.cn/en/product/kundb

Technical documentation

help.sap.com/hana

sphinxsearch.com/docs

Developer

SAP

Sphinx Technologies Inc.

Alex Kashirin

Transwarp

Initial release

2010

2001

2020

Current release

2.0 SPS07 (April 4, 2023), April 2023

3.5.1, February 2023

0.5, April 2021

License

Commercial or Open Source

commercial

Open Source

GPL version 2, commercial licence available

Open Source

GPL V3

commercial

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

Server operating systems

Appliance or cloud-service

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Linux

Data scheme

yes

schema-free

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.

Secondary indexes

yes

full-text index on all search fields

yes

SQL

Support of SQL

yes

SQL-like query language (SphinxQL)

SQL-like query language

yes

APIs and other access methods

JDBC
ODBC

Proprietary protocol

Proprietary protocol
Thrift

Supported programming languages

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

C++

Server-side scripts

Stored procedures

SQLScript, R

yes

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

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

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

User concepts

Access control

yes

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.