DBMS > Dragonfly vs. Newts vs. PouchDB vs. XTDB

System Properties Comparison Dragonfly vs. Newts vs. PouchDB vs. XTDB

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

Time Series DBMS based on Cassandra

JavaScript DBMS with an API inspired by CouchDB

A general purpose database with bitemporal SQL and Datalog and graph queries

Primary database model

Key-value store

Time Series DBMS

Document store

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

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

Score	0.07
Rank	#375	Overall
	#41	Time Series DBMS

Score	2.34
Rank	#112	Overall
	#21	Document stores

Score	0.18
Rank	#332	Overall
	#46	Document stores

Website

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

opennms.github.io/newts

pouchdb.com

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

www.dragonflydb.io/docs

github.com/OpenNMS/newts/wiki

pouchdb.com/guides

www.xtdb.com/docs

Developer

DragonflyDB team and community contributors

OpenNMS Group

Apache Software Foundation

Juxt Ltd.

Initial release

2023

2014

2012

2019

Current release

1.0, March 2023

7.1.1, June 2019

1.19, September 2021

License

Commercial or Open Source

Open Source

BSL 1.1

Open Source

Apache 2.0

Open Source

MIT License

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

Java

JavaScript

Clojure

Server operating systems

Linux

Linux
OS X
Windows

server-less, requires a JavaScript environment (browser, Node.js)

All OS with a Java 8 (and higher) VM
Linux

Data scheme

scheme-free

schema-free

Typing

predefined data types such as float or date

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

yes

yes, extensible-data-notation format

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

via views

yes

SQL

Support of SQL

limited SQL, making use of Apache Calcite

APIs and other access methods

Proprietary protocol

RESP - REdis Serialization Protocol

HTTP REST
Java API

HTTP REST

only for PouchDB Server
JavaScript API

HTTP REST
JDBC

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

Java

JavaScript

Clojure
Java

Server-side scripts

Stored procedures

Lua

View functions in JavaScript

Triggers

publish/subscribe channels provide some trigger functionality

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

based on Cassandra

Sharding

with a proxy-based framework, named couchdb-lounge

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

selectable replication factor

based on Cassandra

Multi-source replication

also with CouchDB databases
Source-replica replication

also with CouchDB databases

yes, each node contains all data

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Eventual Consistency

Foreign keys

Referential integrity

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

by using IndexedDB, WebSQL or LevelDB as backend

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

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

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

New kids on the block: database management systems implemented in JavaScript
1 December 2014, Matthias Gelbmann

show all

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

SFU Computing Science researchers receive 2022 ACM SIGMOD Research Highlight Award.
24 February 2023, Simon Fraser University News

provided by Google News

Building an Offline First App with PouchDB — SitePoint
10 March 2014, SitePoint

Getting Started with PouchDB Client-Side JavaScript Database — SitePoint
7 September 2016, SitePoint

3 Reasons To Think Offline First
22 March 2017, IBM

Create Offline Web Apps Using Service Workers & PouchDB — SitePoint
7 March 2017, SitePoint

Offline-first web and mobile apps: Top frameworks and components
22 January 2019, TechBeacon

provided by Google News

Share this page