DBMS > SAP HANA vs. SiteWhere vs. TerminusDB vs. TinkerGraph

System Properties Comparison SAP HANA vs. SiteWhere vs. TerminusDB vs. TinkerGraph

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

M2M integration platform for persisting/querying time series data

Scalable Graph Database platform making enterprise data available by exploiting inferred entities and relationships

A lightweight, in-memory graph engine that serves as a reference implementation of the TinkerPop3 API

Primary database model

Relational DBMS

Time Series DBMS

Graph DBMS

Secondary database models

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

Document store
RDF store

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

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Score	0.06
Rank	#356	Overall
	#35	Time Series DBMS

Score	0.17
Rank	#325	Overall
	#29	Graph DBMS

Score	0.08
Rank	#348	Overall
	#35	Graph DBMS

Website

www.sap.com/products/hana.html

github.com/sitewhere/sitewhere

terminusdb.com

tinkerpop.apache.org/docs/current/reference/#tinkergraph-gremlin

Technical documentation

help.sap.com/hana

sitewhere1.sitewhere.io/index.html

terminusdb.github.io/terminusdb/#

Developer

SAP

SiteWhere

DataChemist Ltd.

Initial release

2010

2018

2009

Current release

2.0 SPS07 (April 4, 2023), April 2023

11.0.0, January 2023

License

Commercial or Open Source

commercial

Open Source

Common Public Attribution License Version 1.0

Open Source

GPL V3

Open Source

Apache 2.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

Java

Prolog, Rust

Java

Server operating systems

Appliance or cloud-service

Linux
OS X
Windows

Linux

Data scheme

yes

predefined scheme

yes

schema-free

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

SQL-like query language (WOQL)

APIs and other access methods

JDBC
ODBC

HTTP REST

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

TinkerPop 3

Supported programming languages

JavaScript
Python

Groovy
Java

Server-side scripts

Stored procedures

SQLScript, R

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

yes

Sharding

based on HBase

Graph Partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor

based on HBase

Journaling Streams

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

Foreign keys

Referential integrity

yes

Relationships in graphs

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 journaling

optional

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

Users with fine-grained authorization concept

Role-based access control

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.