DBMS > atoti vs. DolphinDB vs. Dragonfly vs. GeoMesa

System Properties Comparison atoti vs. DolphinDB vs. Dragonfly vs. GeoMesa

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

An in-memory DBMS combining transactional and analytical processing to handle the aggregation of ever-changing data.

DolphinDB is a high performance Time Series DBMS. It is integrated with an easy-to-use fully featured programming language and a high-volume high-velocity streaming analytics system. It offers operational simplicity, scalability, fault tolerance, and concurrency.

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

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

Primary database model

Secondary database models

Relational DBMS

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

Score	0.61
Rank	#243	Overall
	#10	Object oriented DBMS

Score	4.03
Rank	#78	Overall
	#6	Time Series DBMS

Score	0.49
Rank	#261	Overall
	#38	Key-value stores

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Website

atoti.io

www.dolphindb.com

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

www.geomesa.org

Technical documentation

docs.atoti.io

docs.dolphindb.cn/en/help200/index.html

www.dragonflydb.io/docs

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

Developer

ActiveViam

DolphinDB, Inc

DragonflyDB team and community contributors

CCRi and others

Initial release

2018

2023

2014

Current release

v2.00.4, January 2022

1.0, March 2023

5.0.0, May 2024

License

Commercial or Open Source

commercial

free versions available

commercial

free community version available

Open Source

BSL 1.1

Open Source

Apache License 2.0

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

Java

C++

Scala

Server operating systems

Linux
Windows

Linux

Data scheme

yes

scheme-free

yes

Typing

predefined data types such as float or date

yes

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

yes

SQL

Support of SQL

Multidimensional Expressions (MDX)

SQL-like query language

APIs and other access methods

JDBC
JSON over HTTP
Kafka
MQTT (Message Queue Telemetry Transport)
ODBC
OPC DA
OPC UA
RabbitMQ
WebSocket

Proprietary protocol

RESP - REdis Serialization Protocol

Supported programming languages

C#
C++
Go
Java
JavaScript
MatLab
Python
R
Rust

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

Server-side scripts

Stored procedures

Python

yes

Lua

Triggers

publish/subscribe channels provide some trigger functionality

Partitioning methods

Methods for storing different data on different nodes

Sharding, horizontal partitioning

horizontal partitioning

depending on storage layer

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

depending on storage layer

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

depending on storage layer

Foreign keys

Referential integrity

Transaction concepts

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

yes

Atomic execution of command blocks and scripts

Concurrency

Support for concurrent manipulation of data

yes, multi-version concurrency control (MVCC)

yes

yes, strict serializability by the server

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

depending on storage layer

User concepts

Access control

Administrators, Users, Groups

Password-based authentication

yes

depending on the DBMS used for storage

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

DB-Engines blog posts

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

Recent citations in the news

FRTB product of the year: ActiveViam
28 November 2023, Risk.net

provided by Google 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

Dragonfly 1.0 Released For What Claims To Be The World's Fastest In-Memory Data Store
20 March 2023, Phoronix

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

provided by Google News

Share this page