DBMS > GeoMesa vs. HugeGraph vs. Microsoft SQL Server vs. OpenQM

System Properties Comparison GeoMesa vs. HugeGraph vs. Microsoft SQL Server vs. OpenQM

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

A fast-speed and highly-scalable Graph DBMS

Microsofts flagship relational DBMS

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

Primary database model

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	0.17
Rank	#335	Overall
	#31	Graph DBMS

Score	821.56
Rank	#3	Overall
	#3	Relational DBMS

Score	0.34
Rank	#284	Overall
	#10	Multivalue DBMS

Website

www.geomesa.org

github.com/hugegraph
hugegraph.apache.org

www.microsoft.com/en-us/sql-server

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

Technical documentation

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

hugegraph.apache.org/docs

learn.microsoft.com/en-US/sql/sql-server

Developer

CCRi and others

Baidu

Microsoft

Rocket Software, originally Martin Phillips

Initial release

2014

2018

1989

1993

Current release

5.0.0, May 2024

0.9

SQL Server 2022, November 2022

3.4-12

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

Apache Version 2.0

commercial

restricted free version is available

Open Source

GPLv2, extended commercial license available

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.

SQLServer Flex @ STACKIT offers a managed version of SQL Server with adjustable CPU, RAM, storage amount and speed, in enterprise grade to perfectly match all application requirements. All services are 100% GDPR-compliant.

Implementation language

Scala

Java

C++

Server operating systems

Linux
macOS
Unix

Linux
Windows

AIX
FreeBSD
Linux
macOS
Raspberry Pi
Solaris
Windows

Data scheme

yes

with some exceptions

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

also supports composite index and range index

yes

SQL

Support of SQL

yes

APIs and other access methods

Java API
RESTful HTTP API
TinkerPop Gremlin

ADO.NET
JDBC
ODBC
OLE DB
Tabular Data Stream (TDS)

Supported programming languages

Groovy
Java
Python

C#
C++
Delphi
Go
Java
JavaScript (Node.js)
PHP
Python
R
Ruby
Visual Basic

.Net
Basic
C
Java
Objective C
PHP
Python

Server-side scripts

Stored procedures

asynchronous Gremlin script jobs

Transact SQL, .NET languages, R, Python and (with SQL Server 2019) Java

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

yes

depending on used storage backend, e.g. Cassandra and HBase

tables can be distributed across several files (horizontal partitioning); sharding through federation

yes

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

yes

depending on used storage backend, e.g. Cassandra and HBase

yes, but depending on the SQL-Server Edition

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via hugegraph-spark

Consistency concepts

Methods to ensure consistency in a distributed system

depending on storage layer

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

edges in graph

yes

Transaction concepts

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

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.

depending on storage layer

yes

User concepts

Access control

yes

depending on the DBMS used for storage

Users, roles and permissions

fine grained access rights according to SQL-standard

Access rights can be defined down to the item level

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.