DBMS > Brytlyt vs. OpenQM vs. SAP HANA vs. SiteWhere

System Properties Comparison Brytlyt vs. OpenQM vs. SAP HANA vs. SiteWhere

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Scalable GPU-accelerated RDBMS for very fast analytic and streaming workloads, leveraging PostgreSQL

QpenQM is a high-performance, self-tuning, multi-value DBMS

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

M2M integration platform for persisting/querying time series data

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	0.29
Rank	#288	Overall
	#131	Relational DBMS

Score	0.27
Rank	#298	Overall
	#10	Multivalue DBMS

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Score	0.06
Rank	#356	Overall
	#35	Time Series DBMS

Website

brytlyt.io

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-open-qm

www.sap.com/products/hana.html

github.com/sitewhere/sitewhere

Technical documentation

docs.brytlyt.io

help.sap.com/hana

sitewhere1.sitewhere.io/index.html

Developer

Brytlyt

Rocket Software, originally Martin Phillips

SAP

SiteWhere

Initial release

2016

1993

2010

Current release

5.0, August 2023

3.4-12

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

commercial

Open Source

GPLv2, extended commercial license available

commercial

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

Java

Server operating systems

Linux
OS X
Windows

AIX
FreeBSD
Linux
macOS
Raspberry Pi
Solaris
Windows

Appliance or cloud-service

Linux
OS X
Windows

Data scheme

yes

with some exceptions

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.

yes

specific XML-type available, but no XML query functionality.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

APIs and other access methods

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

JDBC
ODBC

HTTP REST

Supported programming languages

.Net
C
C++
Delphi
Java
Perl
Python
Tcl

.Net
Basic
C
Java
Objective C
PHP
Python

Server-side scripts

Stored procedures

user defined functions

in PL/pgSQL

yes

SQLScript, R

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

yes

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

selectable replication factor

based on HBase

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

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

Access rights can be defined down to the item level

yes

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.