DBMS > BoltDB vs. GeoMesa vs. Microsoft SQL Server vs. Teradata Aster vs. TerarkDB

System Properties Comparison BoltDB vs. GeoMesa vs. Microsoft SQL Server vs. Teradata Aster vs. TerarkDB

Editorial information provided by DB-Engines

Name

Teradata Aster has been integrated into other Teradata systems and therefore will be removed from the DB-Engines ranking.

Description

An embedded key-value store for Go.

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

Microsofts flagship relational DBMS

Platform for big data analytics on multistructured data sources and types

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
Graph DBMS
Spatial DBMS

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

Score	0.80
Rank	#215	Overall
	#31	Key-value stores

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	821.56
Rank	#3	Overall
	#3	Relational DBMS

Score	0.08
Rank	#367	Overall
	#56	Key-value stores

Website

github.com/boltdb/bolt

www.geomesa.org

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

github.com/bytedance/terarkdb

Technical documentation

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

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

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

Developer

CCRi and others

Microsoft

Teradata

ByteDance, originally Terark

Initial release

2013

2014

1989

2005

2016

Current release

5.0.0, May 2024

SQL Server 2022, November 2022

License

Commercial or Open Source

Open Source

MIT License

Open Source

Apache License 2.0

commercial

restricted free version is available

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.

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

C++

Server operating systems

BSD
Linux
OS X
Solaris
Windows

Linux
Windows

Linux

Data scheme

schema-free

yes

Flexible Schema (defined schema, partial schema, schema free)

defined schema within the relational store; partial schema or schema free in the Aster File Store

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

in Aster File Store

Secondary indexes

yes

SQL

Support of SQL

yes

APIs and other access methods

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

ADO.NET
JDBC
ODBC
OLE DB

C++ API
Java API

Supported programming languages

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

C
C#
C++
Java
Python
R

C++
Java

Server-side scripts

Stored procedures

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

R packages

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

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

depending on storage layer

yes, but depending on the SQL-Server Edition

yes

Dimension tables are replicated across all nodes in the cluster. The number of replicas for the file store can be configured.

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

SQL Map-Reduce Framework

Consistency concepts

Methods to ensure consistency in a distributed system

none

depending on storage layer

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

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

fine grained access rights according to SQL-standard

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.