DBMS > Dragonfly vs. MongoDB vs. SiteWhere

System Properties Comparison Dragonfly vs. MongoDB vs. SiteWhere

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

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

One of the most popular document stores available both as a fully managed cloud service and for deployment on self-managed infrastructure

M2M integration platform for persisting/querying time series data

Primary database model

Key-value store

Document store

Time Series DBMS

Secondary database models

Spatial DBMS
Search engine

integrated Lucene index, currently in MongoDB Atlas only.
Time Series DBMS

Time Series Collections introduced in Release 5.0
Vector DBMS

currently available in the MongoDB Atlas cloud service only

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

Score	0.53
Rank	#244	Overall
	#35	Key-value stores

Score	402.51
Rank	#5	Overall
	#1	Document stores

Score	0.07
Rank	#346	Overall
	#34	Time Series DBMS

Website

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

www.mongodb.com

github.com/sitewhere/sitewhere

Technical documentation

www.dragonflydb.io/docs

www.mongodb.com/docs/manual

sitewhere1.sitewhere.io/index.html

Developer

DragonflyDB team and community contributors

MongoDB, Inc

SiteWhere

Initial release

2023

2009

2010

Current release

1.0, March 2023

7.0.5, January 2024

License

Commercial or Open Source

Open Source

BSL 1.1

Open Source

MongoDB Inc.'s Server Side Public License v1. Prior versions were published under GNU AGPL v3.0. Commercial licenses are also available.

Open Source

Common Public Attribution License Version 1.0

Cloud-based only

Only available as a cloud service

MongoDB available as DBaaS (MongoDB Atlas)

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

C++

Java

Server operating systems

Linux

Linux
OS X
Solaris
Windows

Linux
OS X
Windows

Data scheme

scheme-free

schema-free

Although schema-free, documents of the same collection often follow the same structure. Optionally impose all or part of a schema by defining a JSON schema.

predefined scheme

Typing

predefined data types such as float or date

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

yes

string, integer, double, decimal, boolean, date, object_id, geospatial

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

Read-only SQL queries via the MongoDB Atlas SQL Interface

APIs and other access methods

Proprietary protocol

RESP - REdis Serialization Protocol

GraphQL
HTTP REST
Prisma
proprietary protocol using JSON

HTTP REST

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

Actionscript

unofficial driver
C
C#
C++
Clojure

unofficial driver
ColdFusion

unofficial driver
D

unofficial driver
Dart

unofficial driver
Delphi

unofficial driver
Erlang
Go
Groovy

unofficial driver
Haskell
Java
JavaScript
Kotlin
Lisp

unofficial driver
Lua

unofficial driver
MatLab

unofficial driver
Perl
PHP
PowerShell

unofficial driver
Prolog

unofficial driver
Python
R

unofficial driver
Ruby
Rust
Scala
Smalltalk

unofficial driver
Swift

Server-side scripts

Stored procedures

Lua

JavaScript

Triggers

publish/subscribe channels provide some trigger functionality

yes

in MongoDB Atlas only

Partitioning methods

Methods for storing different data on different nodes

Sharding

Partitioned by hashed, ranged, or zoned sharding keys. Live resharding allows users to change their shard keys as an online operation with zero downtime.

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Multi-Source deployments with MongoDB Atlas Global Clusters
Source-replica replication

selectable replication factor

based on HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

can be individually decided for each read operation
Immediate Consistency

default behaviour

Immediate Consistency

Foreign keys

Referential integrity

typically not used, however similar functionality with DBRef possible

Transaction concepts

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

Atomic execution of command blocks and scripts

Multi-document ACID Transactions with snapshot isolation

Concurrency

Support for concurrent manipulation of data

yes, strict serializability by the server

yes

Durability

Support for making data persistent

yes

optional, enabled by default

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

In-memory storage engine introduced with MongoDB version 3.2

User concepts

Access control

Password-based authentication

Access rights for users and roles

Users with fine-grained authorization concept

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.