DBMS > Dolt vs. GeoMesa vs. Microsoft SQL Server vs. PostGIS vs. TerarkDB

System Properties Comparison Dolt vs. GeoMesa vs. Microsoft SQL Server vs. PostGIS vs. TerarkDB

Editorial information provided by DB-Engines

Name

Description

A MySQL compatible DBMS with Git-like versioning of data and schema

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

Microsofts flagship relational DBMS

Spatial extension of PostgreSQL

A key-value store forked from RocksDB with advanced compression algorithms. It can be used standalone or as a storage engine for MySQL and MongoDB

Primary database model

Secondary database models

Document store

Document store
Graph DBMS
Spatial DBMS

Relational DBMS

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

Score	0.95
Rank	#197	Overall
	#93	Relational DBMS

Score	0.81
Rank	#214	Overall
	#4	Spatial DBMS

Score	829.80
Rank	#3	Overall
	#3	Relational DBMS

Score	23.90
Rank	#29	Overall
	#1	Spatial DBMS

Score	0.04
Rank	#377	Overall
	#58	Key-value stores

Website

github.com/dolthub/dolt
www.dolthub.com

www.geomesa.org

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

postgis.net

github.com/bytedance/terarkdb

Technical documentation

docs.dolthub.com

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

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

postgis.net/documentation

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

Developer

DoltHub Inc

CCRi and others

Microsoft

ByteDance, originally Terark

Initial release

2018

2014

1989

2005

2016

Current release

4.0.5, February 2024

SQL Server 2022, November 2022

3.4.2, February 2024

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

Apache License 2.0

commercial

restricted free version is available

Open Source

GPL v2.0

commercial

restricted open source version 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.

Implementation language

Scala

C++

Server operating systems

Linux
macOS
Windows

Linux
Windows

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

SQL

Support of SQL

yes

APIs and other access methods

CLI Client
HTTP REST

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

C++ API
Java 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

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

C++
Java

Server-side scripts

Stored procedures

yes

currently in alpha release

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

user defined functions

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

depending on storage layer

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

yes

based on PostgreSQL

none

Replication methods

Methods for redundantly storing data on multiple nodes

A database can be cloned to multiple locations and be used there in isolation. Data/schema changes can be pushed/pulled explicitly between locations.

depending on storage layer

yes, but depending on the SQL-Server Edition

yes

based on PostgreSQL

none

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

Immediate Consistency

Foreign keys

Referential integrity

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

Only one user is configurable, and must be specified in the config file at startup

yes

depending on the DBMS used for storage

fine grained access rights according to SQL-standard

yes

based on PostgreSQL

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.