DBMS > Atos Standard Common Repository vs. BoltDB vs. SAP HANA vs. SiteWhere

System Properties Comparison Atos Standard Common Repository vs. BoltDB vs. SAP HANA vs. SiteWhere

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

This system has been discontinued and will be removed from the DB-Engines ranking.

Description

Highly scalable database system, designed for managing session and subscriber data in modern mobile communication networks

An embedded key-value store for Go.

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

M2M integration platform for persisting/querying time series data

Primary database model

Document store
Key-value store

Key-value store

Relational DBMS

Time Series DBMS

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.80
Rank	#215	Overall
	#31	Key-value stores

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Score	0.06
Rank	#383	Overall
	#43	Time Series DBMS

Website

atos.net/en/convergence-creators/portfolio/standard-common-repository

github.com/boltdb/bolt

www.sap.com/products/hana.html

github.com/sitewhere/sitewhere

Technical documentation

help.sap.com/hana

sitewhere1.sitewhere.io/index.html

Developer

Atos Convergence Creators

SAP

SiteWhere

Initial release

2016

2013

2010

Current release

1703

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

commercial

Open Source

MIT License

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

Java

Server operating systems

Linux

BSD
Linux
OS X
Solaris
Windows

Appliance or cloud-service

Linux
OS X
Windows

Data scheme

Schema and schema-less with LDAP views

schema-free

yes

predefined scheme

Typing

predefined data types such as float or date

optional

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

Secondary indexes

yes

SQL

Support of SQL

yes

APIs and other access methods

LDAP

JDBC
ODBC

HTTP REST

Supported programming languages

All languages with LDAP bindings

Server-side scripts

Stored procedures

SQLScript, R

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

none

yes

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

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 or Eventual Consistency depending on configuration

none

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

Atomic execution of specific operations

yes

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

LDAP bind authentication

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.