DBMS > Badger vs. EsgynDB vs. GeoMesa vs. Microsoft SQL Server vs. TerminusDB

System Properties Comparison Badger vs. EsgynDB vs. GeoMesa vs. Microsoft SQL Server vs. TerminusDB

Editorial information provided by DB-Engines

Name

Description

An embeddable, persistent, simple and fast Key-Value Store, written purely in Go.

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

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

Microsofts flagship relational DBMS

Scalable Graph Database platform making enterprise data available by exploiting inferred entities and relationships

Primary database model

Secondary database models

Document store
Graph DBMS
Spatial DBMS

Document store
RDF store

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

Score	0.14
Rank	#331	Overall
	#49	Key-value stores

Score	0.16
Rank	#329	Overall
	#146	Relational DBMS

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	0.17
Rank	#325	Overall
	#29	Graph DBMS

Website

github.com/dgraph-io/badger

www.esgyn.cn

www.geomesa.org

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

terminusdb.com

Technical documentation

godoc.org/github.com/dgraph-io/badger

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

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

terminusdb.github.io/terminusdb/#

Developer

DGraph Labs

Esgyn

CCRi and others

Microsoft

DataChemist Ltd.

Initial release

2017

2015

2014

1989

2018

Current release

4.0.5, February 2024

SQL Server 2022, November 2022

11.0.0, January 2023

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

Open Source

Apache License 2.0

commercial

restricted free version is available

Open Source

GPL V3

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

C++, Java

Scala

C++

Prolog, Rust

Server operating systems

BSD
Linux
OS X
Solaris
Windows

Linux

Linux
Windows

Linux

Data scheme

schema-free

yes

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

SQL-like query language (WOQL)

APIs and other access methods

ADO.NET
JDBC
ODBC

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

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

Supported programming languages

All languages supporting JDBC/ODBC/ADO.Net

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

JavaScript
Python

Server-side scripts

Stored procedures

Java Stored Procedures

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

none

Sharding

depending on storage layer

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

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication between multi datacenters

depending on storage layer

yes, but depending on the SQL-Server Edition

Journaling Streams

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

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 journaling

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

fine grained access rights according to SQL-standard

yes

depending on the DBMS used for storage

fine grained access rights according to SQL-standard

Role-based access control

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.