DBMS > Altibase vs. Google Cloud Datastore vs. RRDtool vs. SiteWhere vs. SQLite

System Properties Comparison Altibase vs. Google Cloud Datastore vs. RRDtool vs. SiteWhere vs. SQLite

Editorial information provided by DB-Engines

Name

Description

An enterprise grade, high-performance RDBMS

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

Industry standard data logging and graphing tool for time series data. RRD is an acronym for round-robin database.

The data is stored in a circular buffer, thus the system storage footprint remains constant over time.

M2M integration platform for persisting/querying time series data

Widely used embeddable, in-process RDBMS

Primary database model

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

Score	1.02
Rank	#189	Overall
	#88	Relational DBMS

Score	4.36
Rank	#72	Overall
	#12	Document stores

Score	1.90
Rank	#132	Overall
	#11	Time Series DBMS

Score	0.06
Rank	#383	Overall
	#43	Time Series DBMS

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Website

altibase.com

cloud.google.com/datastore

oss.oetiker.ch/rrdtool

github.com/sitewhere/sitewhere

www.sqlite.org

Technical documentation

github.com/ALTIBASE/Documents/tree/master/Manuals

cloud.google.com/datastore/docs

oss.oetiker.ch/rrdtool/doc

sitewhere1.sitewhere.io/index.html

www.sqlite.org/docs.html

Developer

Altibase

Google

Tobias Oetiker

SiteWhere

Dwayne Richard Hipp

Initial release

1999

2008

1999

2010

2000

Current release

v7.3, 2023, August 2023

1.8.0, 2022

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

commercial

Open source edition discontinued with March 2023

commercial

Open Source

GPL V2 and FLOSS

Open Source

Common Public Attribution License Version 1.0

Open Source

Public Domain

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

C++

Implementations in Java (e.g. RRD4J) and C# available

Java

Server operating systems

AIX
HP-UX
Linux

hosted

HP-UX
Linux

Linux
OS X
Windows

server-less

Data scheme

yes

schema-free

yes

predefined scheme

yes

dynamic column types

Typing

predefined data types such as float or date

yes

yes, details here

Numeric data only

yes

not rigid because of 'dynamic typing' concept.

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.

Exporting into and restoring from XML files possible

Secondary indexes

yes

SQL

Support of SQL

ANSI SQL-92

SQL-like query language (GQL)

yes

SQL-92 is not fully supported

APIs and other access methods

JDBC
ODBC
Proprietary protocol

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

in-process shared library
Pipes

HTTP REST

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

C
C++
Java

.Net
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

with librrd library
C#

with a different implementation of RRDTool
Java

with a different implementation of RRDTool
JavaScript (Node.js)

with a different implementation of RRDTool
Lua
Perl
PHP

with a wrapper library
Python
Ruby

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Server-side scripts

Stored procedures

stored procedures and stored functions

using Google App Engine

Triggers

yes

Callbacks using the Google Apps Engine

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

based on HBase

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication using Paxos

none

selectable replication factor

based on HBase

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

none

Immediate Consistency

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

yes

Transaction concepts

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

ACID

Concurrency

Support for concurrent manipulation of data

yes

by using the rrdcached daemon

yes

via file-system locks

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 for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

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.