DBMS > GBase vs. GeoMesa vs. Microsoft SQL Server vs. NuoDB vs. Riak TS

System Properties Comparison GBase vs. GeoMesa vs. Microsoft SQL Server vs. NuoDB vs. Riak TS

Editorial information provided by DB-Engines

Name

Description

Widely used RDBMS in China, including analytical, transactional, distributed transactional, and cloud-native data warehousing.

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

Microsofts flagship relational DBMS

NuoDB is a webscale distributed database that supports SQL and ACID transactions

Riak TS is a distributed NoSQL database optimized for time series data and based on Riak KV

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	1.07
Rank	#185	Overall
	#86	Relational DBMS

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	0.89
Rank	#198	Overall
	#92	Relational DBMS

Score	0.20
Rank	#319	Overall
	#27	Time Series DBMS

Website

www.gbase.cn

www.geomesa.org

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

www.3ds.com/nuodb-distributed-sql-database

Technical documentation

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

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

doc.nuodb.com

www.tiot.jp/riak-docs/riak/ts/latest

Developer

General Data Technology Co., Ltd.

CCRi and others

Microsoft

Dassault Systèmes

originally NuoDB, Inc.

Open Source, formerly Basho Technologies

Initial release

2004

2014

1989

2013

2015

Current release

GBase 8a, GBase 8s, GBase 8c

4.0.5, February 2024

SQL Server 2022, November 2022

3.0.0, September 2022

License

Commercial or Open Source

commercial

Open Source

Apache License 2.0

commercial

restricted free version is available

commercial

limited edition free

Open Source

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

C, Java, Python

Scala

C++

Erlang

Server operating systems

Linux

Linux
Windows

hosted

Amazon EC2, Windows Azure, SoftLayer
Linux
OS X
Windows

Linux
OS X

Data 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

restricted

SQL

Support of SQL

Standard with numerous extensions

yes

yes, limited

APIs and other access methods

ADO.NET
C API
JDBC
ODBC

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

ADO.NET
JDBC
ODBC

HTTP API
Native Erlang Interface

Supported programming languages

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

.Net
C
C++
Go
Java
JavaScript
JavaScript (Node.js)
PHP
Python
Ruby

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

Server-side scripts

Stored procedures

user defined functions

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

Java, SQL

Erlang

Triggers

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning (by range, list and hash) and vertical partitioning

depending on storage layer

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

data is dynamically stored/cached on the nodes where it is read/written

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

depending on storage layer

yes, but depending on the SQL-Server Edition

yes

Managed transparently by NuoDB

selectable replication factor

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

depending on storage layer

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

links between datasets can be stored

Transaction concepts

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

ACID

tunable commit protocol

Concurrency

Support for concurrent manipulation of data

yes

MVCC

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

Temporary table

User concepts

Access control

yes

depending on the DBMS used for storage

fine grained access rights according to SQL-standard

Standard SQL roles/ privileges, Administrative Users

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.