DBMS > Dragonfly vs. Riak TS vs. TinkerGraph vs. Yaacomo

System Properties Comparison Dragonfly vs. Riak TS vs. TinkerGraph vs. Yaacomo

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Yaacomo seems to be discontinued and is removed from the DB-Engines ranking

Description

A drop-in Redis replacement that scales vertically to support millions of operations per second and terabyte sized workloads, all on a single instance

Riak TS is a distributed NoSQL database optimized for time series data and based on Riak KV

A lightweight, in-memory graph engine that serves as a reference implementation of the TinkerPop3 API

OpenCL based in-memory RDBMS, designed for efficiently utilizing the hardware via parallel computing

Primary database model

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

Score	0.44
Rank	#255	Overall
	#38	Key-value stores

Score	0.17
Rank	#318	Overall
	#27	Time Series DBMS

Score	0.08
Rank	#345	Overall
	#34	Graph DBMS

Website

github.com/dragonflydb/dragonfly
www.dragonflydb.io

tinkerpop.apache.org/docs/current/reference/#tinkergraph-gremlin

yaacomo.com

Technical documentation

www.dragonflydb.io/docs

www.tiot.jp/riak-docs/riak/ts/latest

Developer

DragonflyDB team and community contributors

Open Source, formerly Basho Technologies

Q2WEB GmbH

Initial release

2023

2015

2009

Current release

1.0, March 2023

3.0.0, September 2022

License

Commercial or Open Source

Open Source

BSL 1.1

Open Source

Apache 2.0

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

Erlang

Java

Server operating systems

Linux

Linux
OS X

Android
Linux
Windows

Data scheme

scheme-free

schema-free

yes

Typing

predefined data types such as float or date

strings, hashes, lists, sets, sorted sets, bit arrays

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.

Secondary indexes

restricted

yes

SQL

Support of SQL

yes, limited

yes

APIs and other access methods

Proprietary protocol

RESP - REdis Serialization Protocol

HTTP API
Native Erlang Interface

TinkerPop 3

JDBC
ODBC

Supported programming languages

C
C#
C++
Clojure
D
Dart
Elixir
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Lisp
Lua
Objective-C
Perl
PHP
Python
R
Ruby
Rust
Scala
Swift
Tcl

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

Groovy
Java

Server-side scripts

Stored procedures

Lua

Erlang

Triggers

publish/subscribe channels provide some trigger functionality

yes

pre-commit hooks and post-commit hooks

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

selectable replication factor

none

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

none

Immediate Consistency

Foreign keys

Referential integrity

links between datasets can be stored

yes

Relationships in graphs

yes

Transaction concepts

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

Atomic execution of command blocks and scripts

ACID

Concurrency

Support for concurrent manipulation of data

yes, strict serializability by the server

yes

Durability

Support for making data persistent

yes

optional

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

Password-based authentication

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

Recent citations in the news

DragonflyDB Announces $21m in New Funding and General Availability
21 March 2023, Business Wire

DragonflyDB reels in $21M for its speedy in-memory database
21 March 2023, SiliconANGLE News

DragonflyDB Raises $21M in Funding
21 March 2023, FinSMEs

Intel Linux Kernel Optimizations Show Huge Benefit For High Core Count Servers
29 March 2023, Phoronix

The Performance Impact Of Intel's Register File Data Sampling "RFDS" Mitigation
15 March 2024, Phoronix

provided by Google News

Is Riak A Good NoSQL Database Option For Enterprises?
1 July 2019, AIM

Best open source databases for IoT applications
26 May 2017, Open Source For You

provided by Google News

Unit testing Apache TinkerPop transactions: From TinkerGraph to Amazon Neptune
3 June 2024, AWS Blog

Simple Deployment of a Graph Database: JanusGraph
12 October 2020, Towards Data Science

Introducing Gremlin query hints for Amazon Neptune
26 February 2019, AWS Blog

provided by Google News

Share this page