DBMS > AnzoGraph DB vs. BoltDB vs. IRONdb vs. RocksDB vs. Teradata Aster

System Properties Comparison AnzoGraph DB vs. BoltDB vs. IRONdb vs. RocksDB vs. Teradata Aster

Editorial information provided by DB-Engines

Name

IRONdb seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

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

Description

Scalable graph database built for online analytics and data harmonization with MPP scaling, high-performance analytical algorithms and reasoning, and virtualization

An embedded key-value store for Go.

A distributed Time Series DBMS with a focus on scalability, fault tolerance and operational simplicity

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

Platform for big data analytics on multistructured data sources and types

Primary database model

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

Score	0.29
Rank	#303	Overall
	#25	Graph DBMS
	#14	RDF stores

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

Score	3.41
Rank	#86	Overall
	#11	Key-value stores

Website

cambridgesemantics.com/anzograph

github.com/boltdb/bolt

www.circonus.com/solutions/time-series-database/

rocksdb.org

Technical documentation

docs.cambridgesemantics.com/anzograph/userdoc/home.htm

docs.circonus.com/irondb/category/getting-started

github.com/facebook/rocksdb/wiki

Developer

Cambridge Semantics

Circonus LLC.

Facebook, Inc.

Teradata

Initial release

2018

2013

2017

2013

2005

Current release

2.3, January 2021

V0.10.20, January 2018

9.2.1, May 2024

License

Commercial or Open Source

commercial

free trial version available

Open Source

MIT License

commercial

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 and C++

C++

Server operating systems

Linux

BSD
Linux
OS X
Solaris
Windows

Linux

Data scheme

Schema-free and OWL/RDFS-schema support

schema-free

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

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

Typing

predefined data types such as float or date

yes

text, numeric, histograms

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

SPARQL and SPARQL* as primary query language. Cypher preview.

SQL-like query language (Circonus Analytics Query Language: CAQL)

yes

APIs and other access methods

Apache Mule
gRPC
JDBC
Kafka
OData access for BI tools
OpenCypher
RESTful HTTP API
SPARQL

HTTP API

C++ API
Java API

ADO.NET
JDBC
ODBC
OLE DB

Supported programming languages

C++
Java
Python

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript
JavaScript (Node.js)
Lisp
Lua
Perl
PHP
Python
R
Ruby
Rust
Scala

C
C++
Go
Java
Perl
Python
Ruby

C
C#
C++
Java
Python
R

Server-side scripts

Stored procedures

user defined functions and aggregates

yes, in Lua

R packages

Triggers

Partitioning methods

Methods for storing different data on different nodes

Automatic sharding

none

Automatic, metric affinity per node

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication in MPP-Cluster

none

configurable replication factor, datacenter aware

yes

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

MapReduce

Offers an API for user-defined Map/Reduce methods

Kerberos/HDFS data loading

yes

SQL Map-Reduce Framework

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency in MPP-Cluster

none

Immediate consistency per node, eventual consistency across nodes

Immediate Consistency or Eventual Consistency depending on configuration

Foreign keys

Referential integrity

not needed in graphs

Transaction concepts

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

ACID

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

Access rights for users and roles

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.