DBMS > atoti vs. BoltDB vs. Dragonfly vs. searchxml vs. Snowflake

System Properties Comparison atoti vs. BoltDB vs. Dragonfly vs. searchxml vs. Snowflake

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.

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

DBMS for structured and unstructured content wrapped with an application server

Cloud-based data warehousing service for structured and semi-structured data

Primary database model

Object oriented DBMS

Key-value store

Native XML DBMS
Search engine

Relational DBMS

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

Score	0.56
Rank	#245	Overall
	#10	Object oriented DBMS

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

Score	0.41
Rank	#266	Overall
	#38	Key-value stores

Score	0.00
Rank	#383	Overall
	#7	Native XML DBMS
	#25	Search engines

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

atoti.io

github.com/boltdb/bolt

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

www.searchxml.net/category/products

www.snowflake.com

Technical documentation

docs.atoti.io

www.dragonflydb.io/docs

www.searchxml.net/support/handouts

docs.snowflake.net/manuals/index.html

Developer

ActiveViam

DragonflyDB team and community contributors

informationpartners gmbh

Snowflake Computing Inc.

Initial release

2013

2023

2015

2014

Current release

1.0, March 2023

1.0

License

Commercial or Open Source

commercial

free versions available

Open Source

MIT License

Open Source

BSL 1.1

commercial

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java

C++

Server operating systems

BSD
Linux
OS X
Solaris
Windows

Linux

Windows

hosted

Data scheme

schema-free

scheme-free

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

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.

yes

Secondary indexes

yes

SQL

Support of SQL

Multidimensional Expressions (MDX)

yes

APIs and other access methods

Proprietary protocol

RESP - REdis Serialization Protocol

RESTful HTTP API
WebDAV
XQuery
XSLT

CLI Client
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

C++

most other programming languages supported via APIs

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

Python

Lua

yes

on the application server

user defined functions

Triggers

publish/subscribe channels provide some trigger functionality

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding, horizontal partitioning

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

none

Source-replica replication

yes

sychronisation to multiple collections

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

none

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

Atomic execution of command blocks and scripts

multiple readers, single writer

ACID

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

User concepts

Access control

Password-based authentication

Domain, group and role-based access control at the document level and for application services

Users with fine-grained authorization concept, user roles and pluggable 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.