DBMS > MaxDB vs. SAP HANA vs. SingleStore vs. SiteWhere

System Properties Comparison MaxDB vs. SAP HANA vs. SingleStore vs. SiteWhere

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A robust and reliable RDBMS optimized to run all major SAP solutions

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

MySQL wire-compliant distributed RDBMS that combines an in-memory row-oriented and a disc-based column-oriented storage with patented universal storage to handle transactional and analytical workloads in one single table type

M2M integration platform for persisting/querying time series data

Primary database model

Relational DBMS

Time Series DBMS

Secondary database models

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

Document store
Spatial DBMS
Time Series DBMS
Vector DBMS

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

Score	2.15
Rank	#115	Overall
	#55	Relational DBMS

Score	41.32
Rank	#23	Overall
	#16	Relational DBMS

Score	4.02
Rank	#74	Overall
	#39	Relational DBMS

Score	0.07
Rank	#347	Overall
	#33	Time Series DBMS

Website

maxdb.sap.com

www.sap.com/products/hana.html

www.singlestore.com

github.com/sitewhere/sitewhere

Technical documentation

maxdb.sap.com/documentation

help.sap.com/hana

docs.singlestore.com

sitewhere1.sitewhere.io/index.html

Developer

SAP, acquired from Software AG (Adabas-D) in 1997

SAP

SingleStore Inc.

SiteWhere

Initial release

1984

2010

2013

2010

Current release

7.9.10.12, February 2024

2.0 SPS07 (April 4, 2023), April 2023

8.5, January 2024

License

Commercial or Open Source

commercial

Limited community edition free

commercial

free developer edition available

Open Source

Common Public Attribution License Version 1.0

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

C++, Go

Java

Server operating systems

AIX
HP-UX
Linux
Solaris
Windows

Appliance or cloud-service

Linux

64 bit version required

Linux
OS X
Windows

Data scheme

yes

predefined scheme

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

SQL

Support of SQL

yes

but no triggers and foreign keys

APIs and other access methods

ADO.NET
JDBC
ODBC
WebDAV

JDBC
ODBC

Cluster Management API

as HTTP Rest and CLI
HTTP API
JDBC
MongoDB API
ODBC

HTTP REST

Supported programming languages

.Net
C#
Java
Perl
PHP
Python

Bash
C
C#
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

SQLScript, R

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

yes

Sharding

hash partitioning

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

Source-replica replication

stores two copies of each physical data partition on two separate nodes

selectable replication factor

based on HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

can define user-defined aggregate functions for map-reduce-style calculations

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

yes, multi-version concurrency control (MVCC)

yes

Durability

Support for making data persistent

yes

All updates are persistent, including those to disk-based columnstores and memory-based row stores. Transaction commits are supported via write-ahead log.

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

fine grained access rights according to SQL-standard

yes

Fine grained access control via users, groups and roles

Users with fine-grained authorization concept

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.