DBMS > Graphite vs. Hazelcast vs. PouchDB vs. Sphinx vs. SQLite

System Properties Comparison Graphite vs. Hazelcast vs. PouchDB vs. Sphinx vs. SQLite

Editorial information provided by DB-Engines

Name

Description

Data logging and graphing tool for time series data

The storage layer (fixed size database) is called Whisper

A widely adopted in-memory data grid

JavaScript DBMS with an API inspired by CouchDB

Open source search engine for searching in data from different sources, e.g. relational databases

Widely used embeddable, in-process RDBMS

Primary database model

Secondary database models

Document store

JSON support with IMDG 3.12

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

Score	4.57
Rank	#73	Overall
	#5	Time Series DBMS

Score	5.97
Rank	#57	Overall
	#6	Key-value stores

Score	2.28
Rank	#115	Overall
	#21	Document stores

Score	5.98
Rank	#56	Overall
	#5	Search engines

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

github.com/graphite-project/graphite-web

Technical documentation

graphite.readthedocs.io

hazelcast.org/imdg/docs

pouchdb.com/guides

sphinxsearch.com/docs

www.sqlite.org/docs.html

Developer

Chris Davis

Hazelcast

Apache Software Foundation

Sphinx Technologies Inc.

Dwayne Richard Hipp

Initial release

2006

2008

2012

2001

2000

Current release

5.3.6, November 2023

7.1.1, June 2019

3.5.1, February 2023

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

Apache Version 2; commercial licenses available

Open Source

GPL version 2, commercial licence available

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

Python

Java

JavaScript

C++

Server operating systems

Linux
Unix

All OS with a Java VM

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

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

server-less

Data scheme

yes

schema-free

yes

dynamic column types

Typing

predefined data types such as float or date

Numeric data only

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.

yes

the object must implement a serialization strategy

Secondary indexes

yes

via views

yes

full-text index on all search fields

yes

SQL

Support of SQL

SQL-like query language

SQL-like query language (SphinxQL)

yes

SQL-92 is not fully supported

APIs and other access methods

HTTP API
Sockets

JCache
JPA
Memcached protocol
RESTful HTTP API

HTTP REST

only for PouchDB Server
JavaScript API

Proprietary protocol

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

JavaScript (Node.js)
Python

.Net
C#
C++
Clojure
Go
Java
JavaScript (Node.js)
Python
Scala

JavaScript

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

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

yes

Event Listeners, Executor Services

View functions in JavaScript

Triggers

yes

Events

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

with a proxy-based framework, named couchdb-lounge

Sharding

Partitioning is done manually, search queries against distributed index is supported

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

Replicated Map

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

none

Immediate Consistency or Eventual Consistency selectable by user

Raft Consensus Algorithm

Eventual Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

one or two-phase-commit; repeatable reads; read commited

ACID

Concurrency

Support for concurrent manipulation of data

yes

locking

yes

via file-system locks

Durability

Support for making data persistent

yes

by using IndexedDB, WebSQL or LevelDB as backend

yes

The original contents of fields are not stored in the Sphinx index.

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

Role-based access control

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.