DBMS > Atos Standard Common Repository vs. Badger vs. Dragonfly vs. PouchDB

System Properties Comparison Atos Standard Common Repository vs. Badger vs. Dragonfly vs. PouchDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

This system has been discontinued and will be removed from the DB-Engines ranking.

Description

Highly scalable database system, designed for managing session and subscriber data in modern mobile communication networks

An embeddable, persistent, simple and fast Key-Value Store, written purely in Go.

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

JavaScript DBMS with an API inspired by CouchDB

Primary database model

Document store
Key-value store

Key-value store

Document store

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

Score	0.14
Rank	#328	Overall
	#48	Key-value stores

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

Score	2.18
Rank	#114	Overall
	#21	Document stores

Website

atos.net/en/convergence-creators/portfolio/standard-common-repository

github.com/dgraph-io/badger

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

pouchdb.com

Technical documentation

godoc.org/github.com/dgraph-io/badger

www.dragonflydb.io/docs

pouchdb.com/guides

Developer

Atos Convergence Creators

DGraph Labs

DragonflyDB team and community contributors

Apache Software Foundation

Initial release

2016

2017

2023

2012

Current release

1703

1.0, March 2023

7.1.1, June 2019

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

BSL 1.1

Open Source

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

JavaScript

Server operating systems

Linux

BSD
Linux
OS X
Solaris
Windows

Linux

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

Data scheme

Schema and schema-less with LDAP views

schema-free

scheme-free

schema-free

Typing

predefined data types such as float or date

optional

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

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

via views

SQL

Support of SQL

APIs and other access methods

LDAP

Proprietary protocol

RESP - REdis Serialization Protocol

HTTP REST

only for PouchDB Server
JavaScript API

Supported programming languages

All languages with LDAP bindings

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

JavaScript

Server-side scripts

Stored procedures

Lua

View functions in JavaScript

Triggers

yes

publish/subscribe channels provide some trigger functionality

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

none

Sharding

with a proxy-based framework, named couchdb-lounge

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

Source-replica replication

Multi-source replication

also with CouchDB databases
Source-replica replication

also with CouchDB databases

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on configuration

none

Eventual Consistency

Foreign keys

Referential integrity

Transaction concepts

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

Atomic execution of specific operations

Atomic execution of command blocks and scripts

Concurrency

Support for concurrent manipulation of data

yes

yes, strict serializability by the server

Durability

Support for making data persistent

yes

by using IndexedDB, WebSQL or LevelDB as backend

In-memory capabilities

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

yes

User concepts

Access control

LDAP bind authentication

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

Dgraph raises $11.5 million for scalable graph database solutions
31 July 2019, VentureBeat

provided by Google News

DragonflyDB Announces $21m in New Funding and General Availability
21 March 2023, businesswire.com

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

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

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

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

provided by Google News

Share this page