DBMS > Apache IoTDB vs. Google BigQuery vs. Graph Engine vs. LMDB vs. SAP Advantage Database Server

System Properties Comparison Apache IoTDB vs. Google BigQuery vs. Graph Engine vs. LMDB vs. SAP Advantage Database Server

Editorial information provided by DB-Engines

Name

SAP Advantage Database Server seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

An IoT native database with high performance for data management and analysis, deployable on the edge and the cloud and integrated with Hadoop, Spark and Flink

Large scale data warehouse service with append-only tables

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

A high performant, light-weight, embedded key-value database library

Low-cost RDBMS with access to ISAM and FoxPro data structures

Primary database model

Time Series DBMS

Relational DBMS

Graph DBMS
Key-value store

Key-value store

Relational DBMS

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

Score	1.18
Rank	#173	Overall
	#15	Time Series DBMS

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	0.61
Rank	#240	Overall
	#21	Graph DBMS
	#35	Key-value stores

Score	1.99
Rank	#125	Overall
	#21	Key-value stores

Website

iotdb.apache.org

cloud.google.com/bigquery

www.graphengine.io

www.symas.com/symas-embedded-database-lmdb

www.sap.com/products/advantage-database-server.html

Technical documentation

iotdb.apache.org/UserGuide/Master/QuickStart/QuickStart.html

cloud.google.com/bigquery/docs

www.graphengine.io/docs/manual

www.lmdb.tech/doc

Developer

Apache Software Foundation

Google

Microsoft

Symas

Sybase, SAP

Initial release

2018

2010

2011

1993

Current release

1.1.0, April 2023

0.9.32, January 2024

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Open Source

MIT License

Open Source

commercial

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

.NET and C

Server operating systems

All OS with a Java VM (>= 1.8)

hosted

.NET

Linux
Unix
Windows

Linux
Windows

Data scheme

yes

schema-free

yes

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

SQL-like query language

yes

APIs and other access methods

JDBC
Native API

RESTful HTTP/JSON API

RESTful HTTP API

.NET Client API
ADO.NET
JDBC
ODBC
OLE DB

Supported programming languages

C
C#
C++
Go
Java
Python
Scala

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C#
C++
F#
Visual Basic

.Net
C
C++
Clojure
Go
Haskell
Java
JavaScript (Node.js)
Lisp
Lua
MatLab
Nim
Objective C
OCaml
Perl
PHP
Python
R
Ruby
Rust
Swift
Tcl

Delphi
Perl
PHP

Server-side scripts

Stored procedures

yes

user defined functions

in JavaScript

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning (by time range) + vertical partitioning (by deviceId)

none

horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication methods; using Raft/IoTConsensus algorithm to ensure strong/eventual data consistency among multiple replicas

none

Multi-source replication

CONFLICT Trigger to resolve replication conflicts
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Integration with Hadoop and Spark

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Strong Consistency with Raft

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

Since BigQuery is designed for querying data

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

caching of (temporary) tables can be configured

User concepts

Access control

yes

Access privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

fine grained access rights according to SQL-standard

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.