DBMS > MySQL vs. PostGIS vs. SiteWhere vs. Spark SQL vs. TempoIQ

System Properties Comparison MySQL vs. PostGIS vs. SiteWhere vs. Spark SQL vs. TempoIQ

Editorial information provided by DB-Engines

Name

TempoIQ seems to be decommissioned. It will be removed from the DB-Engines ranking.

Description

Widely used open source RDBMS

Spatial extension of PostgreSQL

M2M integration platform for persisting/querying time series data

Spark SQL is a component on top of 'Spark Core' for structured data processing

Scalable analytics DBMS for sensor data, provided as a service (SaaS)

Primary database model

Relational DBMS

Key/Value like access via memcached API

Secondary database models

Document store
Spatial DBMS

Relational DBMS

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

Score	1061.34
Rank	#2	Overall
	#2	Relational DBMS

Score	21.72
Rank	#29	Overall
	#1	Spatial DBMS

Score	0.06
Rank	#383	Overall
	#43	Time Series DBMS

Score	18.04
Rank	#33	Overall
	#20	Relational DBMS

Website

www.mysql.com

postgis.net

github.com/sitewhere/sitewhere

spark.apache.org/sql

tempoiq.com (offline)

Technical documentation

dev.mysql.com/doc

postgis.net/documentation

sitewhere1.sitewhere.io/index.html

spark.apache.org/docs/latest/sql-programming-guide.html

Developer

Oracle

since 2010, originally MySQL AB, then Sun

SiteWhere

Apache Software Foundation

TempoIQ

Initial release

1995

2005

2010

2014

2012

Current release

8.4.0, April 2024

3.4.2, February 2024

3.5.0 ( 2.13), September 2023

License

Commercial or Open Source

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

GPL v2.0

Open Source

Common Public Attribution License Version 1.0

Open Source

Apache 2.0

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.

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

Scala

Server operating systems

FreeBSD
Linux
OS X
Solaris
Windows

Linux
OS X
Windows

Data scheme

yes

predefined scheme

yes

schema-free

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

yes

with proprietary extensions

yes

SQL-like DML and DDL statements

APIs and other access methods

ADO.NET
JDBC
ODBC
Proprietary native API

HTTP REST

JDBC
ODBC

HTTP API

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

Java
Python
R
Scala

C#
Java
JavaScript

Node.js
Python
Ruby

Server-side scripts

Stored procedures

yes

proprietary syntax

user defined functions

Triggers

yes

Realtime Alerts

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

yes

based on PostgreSQL

Sharding

based on HBase

yes, utilizing Spark Core

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

yes

based on PostgreSQL

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

Foreign keys

Referential integrity

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

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

yes

based on PostgreSQL

Users with fine-grained authorization concept

simple authentication-based access control

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.