DBMS > Atos Standard Common Repository vs. Heroic vs. PlanetScale vs. SiteWhere vs. SwayDB

System Properties Comparison Atos Standard Common Repository vs. Heroic vs. PlanetScale vs. SiteWhere vs. SwayDB

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

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

Scalable, distributed, serverless MySQL database platform built on top of Vitess

M2M integration platform for persisting/querying time series data

An embeddable, non-blocking, type-safe key-value store for single or multiple disks and in-memory storage

Primary database model

Document store
Key-value store

Secondary database models

Document store
Spatial DBMS

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

Score	0.46
Rank	#265	Overall
	#22	Time Series DBMS

Score	1.49
Rank	#155	Overall
	#72	Relational DBMS

Score	0.06
Rank	#383	Overall
	#43	Time Series DBMS

Score	0.04
Rank	#387	Overall
	#61	Key-value stores

Website

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

github.com/spotify/heroic

planetscale.com

github.com/sitewhere/sitewhere

swaydb.simer.au

Technical documentation

spotify.github.io/heroic

planetscale.com/docs

sitewhere1.sitewhere.io/index.html

Developer

Atos Convergence Creators

Spotify

PlanetScale

SiteWhere

Simer Plaha

Initial release

2016

2014

2020

2010

2018

Current release

1703

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

commercial

Open Source

Common Public Attribution License Version 1.0

Open Source

GNU Affero GPL V3.0

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java

Scala

Server operating systems

Linux

Docker
Linux
macOS

Linux
OS X
Windows

Data scheme

Schema and schema-less with LDAP views

schema-free

yes

predefined scheme

schema-free

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

via Elasticsearch

yes

SQL

Support of SQL

yes

with proprietary extensions

APIs and other access methods

LDAP

HQL (Heroic Query Language, a JSON-based language)
HTTP API

ADO.NET
JDBC
MySQL protocol
ODBC

HTTP REST

Supported programming languages

All languages with LDAP bindings

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Java
Kotlin
Scala

Server-side scripts

Stored procedures

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding

based on HBase

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

selectable replication factor

based on HBase

none

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

Eventual Consistency
Immediate Consistency

Eventual Consistency across shards
Immediate Consistency within a shard

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

Atomic execution of specific operations

ACID at shard level

Atomic execution of operations

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

Users with fine-grained authorization concept

no user groups or 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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

Recent citations in the news

Infographic: What makes a Mobile Operator's setup future proof?
10 February 2024, Atos

provided by Google News

Review: Google Bigtable scales with ease
7 September 2016, InfoWorld

provided by Google News

PlanetScale ends free tier bid, sheds staff in profitability bid
11 March 2024, The Register

PlanetScale forks MySQL to add vector support
1 June 2024, Yahoo Movies Canada

PlanetScale forks MySQL to add vector support
3 October 2023, TechCrunch

PlanetScale Named to Fortune 2023 Best Small Workplaces
31 August 2023, Business Wire

How to Migrate to PlanetScale's Serverless Database
14 October 2021, The New Stack

provided by Google News

SiteWhere: An open platform for connected devices
11 July 2017, Open Source For You

Ten Popular IoT Platforms You Should be Aware of
27 March 2023, Open Source For You

11 Best Open source IoT Platforms To Develop Smart Projects
9 March 2023, H2S Media

provided by Google News

Share this page