DBMS > Interbase vs. Machbase Neo vs. SAP HANA vs. Spark SQL vs. Sphinx

System Properties Comparison Interbase vs. Machbase Neo vs. SAP HANA vs. Spark SQL vs. Sphinx

Editorial information provided by DB-Engines

Name

Description

Light-weight proven RDBMS

originally from Borland

TimeSeries DBMS for AIoT and BigData

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

Spark SQL is a component on top of 'Spark Core' for structured data processing

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

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	4.08
Rank	#75	Overall
	#41	Relational DBMS

Score	0.17
Rank	#337	Overall
	#30	Time Series DBMS

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Score	18.04
Rank	#33	Overall
	#20	Relational DBMS

Score	5.95
Rank	#55	Overall
	#5	Search engines

Website

www.embarcadero.com/products/interbase

machbase.com

www.sap.com/products/hana.html

spark.apache.org/sql

sphinxsearch.com

Technical documentation

docs.embarcadero.com/products/interbase

machbase.com/dbms

help.sap.com/hana

spark.apache.org/docs/latest/sql-programming-guide.html

sphinxsearch.com/docs

Developer

Embarcadero

Machbase

SAP

Apache Software Foundation

Sphinx Technologies Inc.

Initial release

1984

2013

2010

2014

2001

Current release

InterBase 2020, December 2019

V8.0, August 2023

2.0 SPS07 (April 4, 2023), April 2023

3.5.0 ( 2.13), September 2023

3.5.1, February 2023

License

Commercial or Open Source

commercial

free test version available

commercial

Open Source

Apache 2.0

Open Source

GPL version 2, commercial licence available

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

Scala

C++

Server operating systems

Android
iOS
Linux
OS X
Windows

Linux
macOS
Windows

Appliance or cloud-service

Linux
OS X
Windows

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Data scheme

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.

export as XML data possible

Secondary indexes

yes

full-text index on all search fields

SQL

Support of SQL

yes

SQL-like query language

yes

SQL-like DML and DDL statements

SQL-like query language (SphinxQL)

APIs and other access methods

ADO.NET
JDBC
ODBC

gRPC
HTTP REST
JDBC
MQTT (Message Queue Telemetry Transport)
ODBC

JDBC
ODBC

Proprietary protocol

Supported programming languages

.Net
C
C++
Delphi
Java
Object Pascal
PHP
Ruby

C
C#
C++
Go
Java
JavaScript
PHP

via ODBC
Python
R

via ODBC
Scala

Java
Python
R
Scala

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

Server-side scripts

Stored procedures

yes

Interbase procedure and trigger language

SQLScript, R

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

yes

yes, utilizing Spark Core

Sharding

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

Replication methods

Methods for redundantly storing data on multiple nodes

Interbase Change Views

selectable replication factor

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

Multiversion concurreny control

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

volatile and lookup table

yes

User concepts

Access control

fine grained access rights according to SQL-standard

simple password-based 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.