DBMS > eXtremeDB vs. GeoSpock vs. Google Cloud Firestore vs. OpenQM vs. SQLite

System Properties Comparison eXtremeDB vs. GeoSpock vs. Google Cloud Firestore vs. OpenQM vs. SQLite

Editorial information provided by DB-Engines

Name

GeoSpock seems to be discontinued. Therefore it will be excluded from the DB-Engines ranking.

Description

Natively in-memory DBMS with options for persistency, high-availability and clustering

Spatial and temporal data processing engine for extreme data scale

Cloud Firestore is an auto-scaling document database for storing, syncing, and querying data for mobile and web apps. It offers seamless integration with other Firebase and Google Cloud Platform products.

QpenQM is a high-performance, self-tuning, multi-value DBMS

Widely used embeddable, in-process RDBMS

Primary database model

Relational DBMS
Time Series DBMS

Secondary database models

Time Series DBMS

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

Score	0.74
Rank	#223	Overall
	#103	Relational DBMS
	#18	Time Series DBMS

Score	7.85
Rank	#51	Overall
	#8	Document stores

Score	0.27
Rank	#298	Overall
	#10	Multivalue DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

www.mcobject.com

geospock.com

firebase.google.com/products/firestore

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

www.sqlite.org

Technical documentation

www.mcobject.com/docs/extremedb.htm

firebase.google.com/docs/firestore

www.sqlite.org/docs.html

Developer

McObject

GeoSpock

Google

Rocket Software, originally Martin Phillips

Dwayne Richard Hipp

Initial release

2001

2017

1993

2000

Current release

8.2, 2021

2.0, September 2019

3.4-12

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

commercial

Open Source

GPLv2, extended commercial license available

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 and C++

Java, Javascript

Server operating systems

AIX
HP-UX
Linux
macOS
Solaris
Windows

hosted

AIX
FreeBSD
Linux
macOS
Raspberry Pi
Solaris
Windows

server-less

Data scheme

yes

schema-free

yes

with some exceptions

yes

dynamic column types

Typing

predefined data types such as float or date

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.

support of XML interfaces available

yes

Secondary indexes

yes

temporal, categorical

yes

SQL

Support of SQL

yes

with the option: eXtremeSQL

ANSI SQL for query only (using Presto)

yes

SQL-92 is not fully supported

APIs and other access methods

.NET Client API
JDBC
JNI
ODBC
Proprietary protocol
RESTful HTTP API

JDBC

Android
gRPC (using protocol buffers) API
iOS
JavaScript API
RESTful HTTP API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

.Net
C
C#
C++
Java
Lua
Python
Scala

Go
Java
JavaScript
JavaScript (Node.js)
Objective-C
Python

.Net
Basic
C
Java
Objective C
PHP
Python

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

yes

yes, Firebase Rules & Cloud Functions

yes

Triggers

yes

by defining events

yes, with Cloud Functions

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning / sharding

Automatic sharding

Sharding

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

Active Replication Fabric™ for IoT
Multi-source replication

by means of eXtremeDB Cluster option
Source-replica replication

by means of eXtremeDB High Availability option

Multi-source replication

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Using Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

yes

ACID

Concurrency

Support for concurrent manipulation of data

yes

Optimistic (MVCC) and pessimistic (locking) strategies available

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

Access rights for users can be defined per table

Access rights for users, groups and roles based on Google Cloud Identity and Access Management. Security Rules for 3rd party authentication using Firebase Auth.

Access rights can be defined down to the item level

More information provided by the system vendor

Specific characteristics

eXtremeDB is an in-memory and/or persistent database system that offers an ultra-small...
» more

Competitive advantages

eXtremeDB databases can be modeled relationally or as objects and can utilize SQL...
» more

Typical application scenarios

IoT application across all markets: Industrial Control, Netcom, Telecom, Defense,...
» more

Key customers

Schneider Electronics, F5 Networks, TNS, Boeing, Northrop Grumman, GoPro, ViaSat,...
» more

Market metrics

With hundreds of customers and over 30 million devices/applications using the product...
» more

Licensing and pricing models

For server use cases, there is a simple per-server license irrespective of the number...
» more

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.