DBMS > BoltDB vs. MySQL vs. Postgres-XL vs. Sadas Engine vs. TigerGraph

System Properties Comparison BoltDB vs. MySQL vs. Postgres-XL vs. Sadas Engine vs. TigerGraph

Editorial information provided by DB-Engines

Name

Description

An embedded key-value store for Go.

Widely used open source RDBMS

Based on PostgreSQL enhanced with MPP and write-scale-out cluster features

SADAS Engine is a columnar DBMS specifically designed for high performance in data warehouse environments

A complete, distributed, parallel graph computing platform supporting web-scale data analytics in real-time

Primary database model

Key-value store

Relational DBMS

Key/Value like access via memcached API

Relational DBMS

Graph DBMS

Secondary database models

Document store
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	1061.34
Rank	#2	Overall
	#2	Relational DBMS

Score	0.53
Rank	#254	Overall
	#117	Relational DBMS

Score	0.07
Rank	#373	Overall
	#157	Relational DBMS

Score	1.80
Rank	#138	Overall
	#13	Graph DBMS

Website

github.com/boltdb/bolt

Technical documentation

dev.mysql.com/doc

www.postgres-xl.org/documentation

www.sadasengine.com/en/sadas-engine-download-free-trial-and-documentation/#documentation

docs.tigergraph.com

Developer

Oracle

since 2010, originally MySQL AB, then Sun

SADAS s.r.l.

Initial release

2013

1995

2014

since 2012, originally named StormDB

2006

2017

Current release

8.4.0, April 2024

10 R1, October 2018

8.0

License

Commercial or Open Source

Open Source

MIT License

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

Mozilla public license

commercial

free trial version available

commercial

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.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

C and C++

C++

Server operating systems

BSD
Linux
OS X
Solaris
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Linux
macOS

AIX
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

XML type, but no XML query functionality

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

yes

distributed, parallel query execution

yes

SQL-like query language (GSQL)

APIs and other access methods

ADO.NET
JDBC
ODBC
Proprietary native API

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

JDBC
ODBC
Proprietary protocol

GSQL (TigerGraph Query Language)
Kafka
RESTful HTTP/JSON 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

.Net
C
C++
Delphi
Erlang
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

.Net
C
C#
C++
Groovy
Java
PHP
Python

C++
Java

Server-side scripts

Stored procedures

yes

proprietary syntax

user defined functions

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication
Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

Relationships in graphs

Transaction concepts

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

yes

ACID

not for MyISAM storage engine

ACID

MVCC

ACID

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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.

yes

managed by 'Learn by Usage'

User concepts

Access control

Users with fine-grained authorization concept

no user groups or roles

fine grained access rights according to SQL-standard

Access rights for users, groups and roles 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.