DBMS > Apache IoTDB vs. Google Cloud Spanner vs. jBASE vs. PostGIS

System Properties Comparison Apache IoTDB vs. Google Cloud Spanner vs. jBASE vs. PostGIS

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

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

A horizontally scalable, globally consistent, relational database service. It is the externalization of the core Google database that runs the biggest aspects of Google, like Ads and Google Play.

A robust multi-value DBMS comprising development tools and middleware

Spatial extension of PostgreSQL

Primary database model

Secondary database models

Relational DBMS

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

Score	1.31
Rank	#164	Overall
	#14	Time Series DBMS

Score	2.84
Rank	#100	Overall
	#51	Relational DBMS

Score	1.49
Rank	#156	Overall
	#3	Multivalue DBMS

Score	21.72
Rank	#29	Overall
	#1	Spatial DBMS

Website

iotdb.apache.org

cloud.google.com/spanner

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-jbase

postgis.net

Technical documentation

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

cloud.google.com/spanner/docs

docs.rocketsoftware.com/bundle?labelkey=jbase_5.9

postgis.net/documentation

Developer

Apache Software Foundation

Google

Rocket Software (formerly Zumasys)

Initial release

2018

2017

1991

2005

Current release

1.1.0, April 2023

5.7

3.4.2, February 2024

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Open Source

GPL v2.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

Server operating systems

All OS with a Java VM (>= 1.8)

hosted

AIX
Linux
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

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

SQL-like query language

yes

Query statements complying to ANSI 2011

Embedded SQL for jBASE in BASIC

yes

APIs and other access methods

JDBC
Native API

gRPC (using protocol buffers) API
JDBC

At present, JDBC supports read-only queries. No support for DDL or DML statements.
RESTful HTTP API

JDBC
ODBC
Proprietary protocol
RESTful HTTP API
SOAP-based API

Supported programming languages

C
C#
C++
Go
Java
Python
Scala

Go
Java
JavaScript (Node.js)
Python

.Net
Basic
Jabbascript
Java

Server-side scripts

Stored procedures

yes

user defined functions

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

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

Sharding

yes

based on PostgreSQL

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

Multi-source replication with 3 replicas for regional instances.

yes

based on PostgreSQL

MapReduce

Offers an API for user-defined Map/Reduce methods

Integration with Hadoop and Spark

yes

using Google Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Strong Consistency with Raft

Immediate Consistency

Foreign keys

Referential integrity

yes

by using interleaved tables, this features focuses more on performance improvements than on referential integrity

yes

Transaction concepts

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

ACID

Strict serializable isolation

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

yes

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

Access rights can be defined down to the item level

yes

based on PostgreSQL

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

DB-Engines blog posts

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

Recent citations in the news

TsFile: A Standard Format for IoT Time Series Data
27 February 2024, The New Stack

Linux 6.5 With AMD P-State EPP Default Brings Performance & Power Efficiency Benefits For Ryzen Servers
21 September 2023, Phoronix

AMD EPYC 8324P / 8324PN Siena 32-Core Siena Linux Server Performance Review
10 October 2023, Phoronix

Apache Promotes IoT Database Project
25 September 2020, Datanami

Timecho Raises Over US$10M in First Funding
29 June 2022, FinSMEs

provided by Google News

Google Improves Cloud Spanner: More Compute and Storage without Price Increase
14 October 2023, InfoQ.com

Google makes its Cloud Spanner database service faster and more cost-efficient
11 October 2023, SiliconANGLE News

Google turns up the heat on AWS, claims Cloud Spanner is half the cost of DynamoDB
11 October 2023, TechCrunch

Google Cloud just fired a major volley at AWS as the cloud wars heat up
12 October 2023, TechRadar

Google Spanner: When Do You Need to Move to It?
11 September 2023, hackernoon.com

provided by Google News

Share this page