DBMS > Geode vs. Memcached vs. PouchDB vs. SiteWhere vs. SQLite

System Properties Comparison Geode vs. Memcached vs. PouchDB vs. SiteWhere vs. SQLite

Editorial information provided by DB-Engines

Name

Description

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

In-memory key-value store, originally intended for caching

JavaScript DBMS with an API inspired by CouchDB

M2M integration platform for persisting/querying time series data

Widely used embeddable, in-process RDBMS

Primary database model

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

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

Score	19.42
Rank	#32	Overall
	#4	Key-value stores

Score	2.28
Rank	#115	Overall
	#21	Document stores

Score	0.06
Rank	#356	Overall
	#35	Time Series DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

geode.apache.org

www.memcached.org

pouchdb.com

github.com/sitewhere/sitewhere

www.sqlite.org

Technical documentation

geode.apache.org/docs

github.com/memcached/memcached/wiki

pouchdb.com/guides

sitewhere1.sitewhere.io/index.html

www.sqlite.org/docs.html

Developer

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

Danga Interactive

originally developed by Brad Fitzpatrick for LiveJournal

Apache Software Foundation

SiteWhere

Dwayne Richard Hipp

Initial release

2002

2003

2012

2010

2000

Current release

1.1, February 2017

1.6.25, March 2024

7.1.1, June 2019

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available as Gemfire

Open Source

BSD license

Open Source

Common Public Attribution License Version 1.0

Open Source

Public Domain

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

JavaScript

Java

Server operating systems

All OS with a Java VM

the JDK (8 or later) is also required

FreeBSD
Linux
OS X
Unix
Windows

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

Linux
OS X
Windows

server-less

Data scheme

schema-free

predefined scheme

yes

dynamic column types

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

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

SQL-like query language (OQL)

yes

SQL-92 is not fully supported

APIs and other access methods

Java Client API
Memcached protocol
RESTful HTTP API

Proprietary protocol

HTTP REST

only for PouchDB Server
JavaScript API

HTTP REST

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

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

.Net
C
C++
ColdFusion
Erlang
Java
Lisp
Lua
OCaml
Perl
PHP
Python
Ruby

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

Server-side scripts

Stored procedures

user defined functions

View functions in JavaScript

Triggers

yes

Cache Event Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

with a proxy-based framework, named couchdb-lounge

Sharding

based on HBase

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

none

Repcached, a Memcached patch, provides this functionallity

Multi-source replication

also with CouchDB databases
Source-replica replication

also with CouchDB databases

selectable replication factor

based on HBase

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes, on a single node

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

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

Access rights per client and object definable

yes

using SASL (Simple Authentication and Security Layer) protocol

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.