DBMS > GeoMesa vs. mSQL vs. OpenQM vs. OrigoDB vs. searchxml

System Properties Comparison GeoMesa vs. mSQL vs. OpenQM vs. OrigoDB vs. searchxml

Editorial information provided by DB-Engines

Name

Description

GeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.

mSQL (Mini SQL) is a simple and lightweight RDBMS

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

A fully ACID in-memory object graph database

DBMS for structured and unstructured content wrapped with an application server

Primary database model

Spatial DBMS

Relational DBMS

Multivalue DBMS

Document store
Object oriented DBMS

Native XML DBMS
Search engine

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

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	1.27
Rank	#167	Overall
	#77	Relational DBMS

Score	0.27
Rank	#298	Overall
	#10	Multivalue DBMS

Score	0.00
Rank	#383	Overall
	#53	Document stores
	#20	Object oriented DBMS

Score	0.00
Rank	#383	Overall
	#7	Native XML DBMS
	#25	Search engines

Website

www.geomesa.org

hughestech.com.au/products/msql

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

origodb.com

www.searchxml.net/category/products

Technical documentation

www.geomesa.org/documentation/stable/user/index.html

origodb.com/docs

www.searchxml.net/support/handouts

Developer

CCRi and others

Hughes Technologies

Rocket Software, originally Martin Phillips

Robert Friberg et al

informationpartners gmbh

Initial release

2014

1994

1993

2009

under the name LiveDB

2015

Current release

4.0.5, February 2024

4.4, October 2021

3.4-12

1.0

License

Commercial or Open Source

Open Source

Apache License 2.0

commercial

free licenses can be provided

Open Source

GPLv2, extended commercial license available

Open Source

commercial

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Scala

C++

Server operating systems

AIX
HP-UX
Linux
OS X
Solaris SPARC/x86
Windows

AIX
FreeBSD
Linux
macOS
Raspberry Pi
Solaris
Windows

Linux
Windows

Windows

Data scheme

yes

with some exceptions

yes

schema-free

Typing

predefined data types such as float or date

yes

User defined using .NET types and collections

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

can be achieved using .NET

yes

Secondary indexes

yes

SQL

Support of SQL

A subset of ANSI SQL is implemented

no subqueries, aggregate functions, views, foreign keys, triggers

APIs and other access methods

JDBC
ODBC

.NET Client API
HTTP API
LINQ

RESTful HTTP API
WebDAV
XQuery
XSLT

Supported programming languages

C
C++
Delphi
Java
Perl
PHP
Tcl

.Net
Basic
C
Java
Objective C
PHP
Python

.Net

C++

most other programming languages supported via APIs

Server-side scripts

Stored procedures

yes

on the application server

Triggers

yes

Domain Events

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

none

yes

horizontal partitioning

client side managed; servers are not synchronized

none

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

none

yes

Source-replica replication

yes

sychronisation to multiple collections

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

depending on storage layer

none

Immediate Consistency

Foreign keys

Referential integrity

depending on model

Transaction concepts

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

ACID

multiple readers, single writer

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Write ahead log

yes

In-memory capabilities

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

depending on storage layer

yes

User concepts

Access control

yes

depending on the DBMS used for storage

Access rights can be defined down to the item level

Role based authorization

Domain, group and role-based access control at the document level and for application services

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

Writing a Web Service in Perl
9 July 2003, PCQuest

Higher Education PS rules out ghost students before PAC
29 November 2018, diggers.news

provided by Google News

Share this page