DBMS > Databend vs. Geode vs. PouchDB vs. SQLite vs. WakandaDB

System Properties Comparison Databend vs. Geode vs. PouchDB vs. SQLite vs. WakandaDB

Editorial information provided by DB-Engines

Name

Description

An open-source, elastic, and workload-aware cloud data warehouse designed to meet businesses' massive-scale analytics needs at low cost and with low complexity

Geode is a distributed data container, pooling memory, CPU, network resources, and optionally local disk across multiple processes

JavaScript DBMS with an API inspired by CouchDB

Widely used embeddable, in-process RDBMS

WakandaDB is embedded in a server that provides a REST API and a server-side javascript engine to access data

Primary database model

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

Score	0.30
Rank	#287	Overall
	#130	Relational DBMS

Score	1.92
Rank	#131	Overall
	#23	Key-value stores

Score	2.28
Rank	#115	Overall
	#21	Document stores

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Score	0.03
Rank	#364	Overall
	#17	Object oriented DBMS

Website

github.com/datafuselabs/databend
www.databend.com

Technical documentation

docs.databend.com

geode.apache.org/docs

pouchdb.com/guides

www.sqlite.org/docs.html

wakanda.github.io/doc

Developer

Databend Labs

Originally developed by Gemstone. They outsourced the project to Apache in 2015 but still deliver a commercial version as Gemfire.

Apache Software Foundation

Dwayne Richard Hipp

Wakanda SAS

Initial release

2021

2002

2012

2000

2012

Current release

1.0.59, April 2023

1.1, February 2017

7.1.1, June 2019

3.46.0 (23 May 2024), May 2024

2.7.0 (April 29, 2019), April 2019

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

Apache Version 2; commercial licenses available as Gemfire

Open Source

Public Domain

Open Source

AGPLv3, extended commercial license available

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

Rust

Java

JavaScript

C++, JavaScript

Server operating systems

hosted
Linux
macOS

All OS with a Java VM

the JDK (8 or later) is also required

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

server-less

Linux
OS X
Windows

Data scheme

yes

schema-free

yes

dynamic column types

yes

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

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

via views

yes

SQL

Support of SQL

yes

SQL-like query language (OQL)

yes

SQL-92 is not fully supported

APIs and other access methods

CLI Client
JDBC
RESTful HTTP API

Java Client API
Memcached protocol
RESTful HTTP API

HTTP REST

only for PouchDB Server
JavaScript API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

RESTful HTTP API

Supported programming languages

Go
Java
JavaScript (Node.js)
Python
Rust

.Net
All JVM based languages
C++
Groovy
Java
Scala

JavaScript

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

JavaScript

Server-side scripts

Stored procedures

user defined functions

View functions in JavaScript

yes

Triggers

yes

Cache Event Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

with a proxy-based framework, named couchdb-lounge

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication

also with CouchDB databases
Source-replica replication

also with CouchDB databases

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

yes, on a single node

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

yes

Durability

Support for making data persistent

yes

by using IndexedDB, WebSQL or LevelDB as backend

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

Users with fine-grained authorization concept, user roles

Access rights per client and object definable

yes

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.