DBMS > BigObject vs. MySQL vs. OpenTenBase vs. SiteWhere

System Properties Comparison BigObject vs. MySQL vs. OpenTenBase vs. SiteWhere

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Analytic DBMS for real-time computations and queries

Widely used open source RDBMS

An enterprise-level distributed HTAP open source database based on PostgreSQL

M2M integration platform for persisting/querying time series data

Primary database model

Relational DBMS

a hierachical model (tree) can be imposed

Relational DBMS

Key/Value like access via memcached API

Relational DBMS

Time Series DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	0.19
Rank	#329	Overall
	#146	Relational DBMS

Score	1061.34
Rank	#2	Overall
	#2	Relational DBMS

Score	0.08
Rank	#370	Overall
	#156	Relational DBMS

Score	0.06
Rank	#383	Overall
	#43	Time Series DBMS

Website

bigobject.io

www.mysql.com

github.com/OpenTenBase/OpenTenBase
www.opentenbase.org

github.com/sitewhere/sitewhere

Technical documentation

docs.bigobject.io

dev.mysql.com/doc

docs.opentenbase.org
docs.opentenbase.org/en

sitewhere1.sitewhere.io/index.html

Developer

BigObject, Inc.

Oracle

since 2010, originally MySQL AB, then Sun

OpenAtom Foundation, previously Tencent

SiteWhere

Initial release

2015

1995

2010

Current release

8.4.0, April 2024

2.5, January 2024

License

Commercial or Open Source

commercial

free community edition available

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

BSD-3

Open Source

Common Public Attribution License Version 1.0

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

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

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

C and C++

Java

Server operating systems

Linux

distributed as a docker-image
OS X

distributed as a docker-image (boot2docker)
Windows

distributed as a docker-image (boot2docker)

FreeBSD
Linux
OS X
Solaris
Windows

Linux

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.

yes

Secondary indexes

yes

SQL

Support of SQL

SQL-like DML and DDL statements

yes

with proprietary extensions

yes

APIs and other access methods

fluentd
ODBC
RESTful HTTP API

ADO.NET
JDBC
ODBC
Proprietary native API

HTTP REST

Supported programming languages

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

C
Go
Java
PHP
Python

Server-side scripts

Stored procedures

Lua

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication
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

none

Immediate Consistency

Foreign keys

Referential integrity

yes

automatically between fact table and dimension tables

yes

not for MyISAM storage engine

yes

Transaction concepts

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

ACID

not for MyISAM storage engine

ACID

Concurrency

Support for concurrent manipulation of data

yes

Read/write lock on objects (tables, trees)

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

Users with fine-grained authorization concept

no user groups or roles

Access rights for users, groups and roles according to SQL-standard

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.