DBMS > Badger vs. Drizzle vs. Microsoft SQL Server vs. PouchDB

System Properties Comparison Badger vs. Drizzle vs. Microsoft SQL Server vs. PouchDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Drizzle has published its last release in September 2012. The open-source project is discontinued and Drizzle is excluded from the DB-Engines ranking.

Description

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

MySQL fork with a pluggable micro-kernel and with an emphasis of performance over compatibility.

Microsofts flagship relational DBMS

JavaScript DBMS with an API inspired by CouchDB

Primary database model

Key-value store

Relational DBMS

Document store

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

Score	0.14
Rank	#331	Overall
	#49	Key-value stores

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	2.28
Rank	#115	Overall
	#21	Document stores

Website

github.com/dgraph-io/badger

www.microsoft.com/en-us/sql-server

pouchdb.com

Technical documentation

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

learn.microsoft.com/en-US/sql/sql-server

pouchdb.com/guides

Developer

DGraph Labs

Drizzle project, originally started by Brian Aker

Microsoft

Apache Software Foundation

Initial release

2017

2008

1989

2012

Current release

7.2.4, September 2012

SQL Server 2022, November 2022

7.1.1, June 2019

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

GNU GPL

commercial

restricted free version is available

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.

SQLServer Flex @ STACKIT offers a managed version of SQL Server with adjustable CPU, RAM, storage amount and speed, in enterprise grade to perfectly match all application requirements. All services are 100% GDPR-compliant.

Implementation language

C++

JavaScript

Server operating systems

BSD
Linux
OS X
Solaris
Windows

FreeBSD
Linux
OS X

Linux
Windows

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

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

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

via views

SQL

Support of SQL

yes

with proprietary extensions

yes

APIs and other access methods

JDBC

ADO.NET
JDBC
ODBC
OLE DB
Tabular Data Stream (TDS)

HTTP REST

only for PouchDB Server
JavaScript API

Supported programming languages

C
C++
Java
PHP

C#
C++
Delphi
Go
Java
JavaScript (Node.js)
PHP
Python
R
Ruby
Visual Basic

JavaScript

Server-side scripts

Stored procedures

Transact SQL, .NET languages, R, Python and (with SQL Server 2019) Java

View functions in JavaScript

Triggers

hooks for callbacks inside the server can be used.

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

tables can be distributed across several files (horizontal partitioning); sharding through federation

Sharding

with a proxy-based framework, named couchdb-lounge

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication
Source-replica replication

yes, but depending on the SQL-Server Edition

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

none

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

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

Pluggable authentication mechanisms

e.g. LDAP, HTTP

fine grained access rights according to SQL-standard

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.