DBMS > BoltDB vs. Postgres-XL vs. RocksDB vs. TigerGraph vs. VelocityDB

System Properties Comparison BoltDB vs. Postgres-XL vs. RocksDB vs. TigerGraph vs. VelocityDB

Editorial information provided by DB-Engines

Name

Description

An embedded key-value store for Go.

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

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

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

A .NET Object Database that can be embedded/distributed and extended to a graph data model (VelocityGraph)

Primary database model

Graph DBMS
Object oriented DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	0.74
Rank	#220	Overall
	#31	Key-value stores

Score	0.49
Rank	#256	Overall
	#117	Relational DBMS

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Score	1.83
Rank	#139	Overall
	#13	Graph DBMS

Score	0.05
Rank	#358	Overall
	#36	Graph DBMS
	#16	Object oriented DBMS

Website

github.com/boltdb/bolt

Technical documentation

www.postgres-xl.org/documentation

github.com/facebook/rocksdb/wiki

docs.tigergraph.com

velocitydb.com/UserGuide

Developer

Facebook, Inc.

VelocityDB Inc

Initial release

2013

2014

since 2012, originally named StormDB

2013

2017

2011

Current release

10 R1, October 2018

8.11.4, April 2024

7.x

License

Commercial or Open Source

Open Source

MIT License

Open Source

Mozilla public license

Open Source

BSD

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.

Implementation language

C++

Server operating systems

BSD
Linux
OS X
Solaris
Windows

Linux
macOS

Linux

Any that supports .NET

Data scheme

schema-free

yes

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

distributed, parallel query execution

SQL-like query language (GSQL)

APIs and other access methods

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

C++ API
Java API

GSQL (TigerGraph Query Language)
Kafka
RESTful HTTP/JSON API

.Net

Supported programming languages

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

C
C++
Go
Java
Perl
Python
Ruby

C++
Java

.Net

Server-side scripts

Stored procedures

user defined functions

yes

Triggers

yes

Callbacks are triggered when data changes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

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

Relationships in graphs

Transaction concepts

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

yes

ACID

MVCC

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.

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Role-based access control

Based on Windows Authentication

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.