DBMS > Apache Phoenix vs. Elasticsearch vs. PouchDB vs. SQLite

System Properties Comparison Apache Phoenix vs. Elasticsearch vs. PouchDB vs. SQLite

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A scale-out RDBMS with evolutionary schema built on Apache HBase

A distributed, RESTful modern search and analytics engine based on Apache Lucene

Elasticsearch lets you perform and combine many types of searches such as structured, unstructured, geo, and metric

JavaScript DBMS with an API inspired by CouchDB

Widely used embeddable, in-process RDBMS

Primary database model

Secondary database models

Document store
Spatial DBMS
Vector DBMS

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

Score	2.02
Rank	#130	Overall
	#63	Relational DBMS

Score	134.78
Rank	#7	Overall
	#1	Search engines

Score	2.35
Rank	#116	Overall
	#22	Document stores

Score	116.01
Rank	#10	Overall
	#7	Relational DBMS

Website

phoenix.apache.org

www.elastic.co/elasticsearch

pouchdb.com

www.sqlite.org

Technical documentation

phoenix.apache.org

www.elastic.co/guide/en/elasticsearch/reference/current/index.html

pouchdb.com/guides

www.sqlite.org/docs.html

Developer

Apache Software Foundation

Elastic

Apache Software Foundation

Dwayne Richard Hipp

Initial release

2014

2010

2012

2000

Current release

5.0-HBase2, July 2018 and 4.15-HBase1, December 2019

8.6, January 2023

7.1.1, June 2019

3.45.2 (12 March 2024), March 2024

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

Elastic License

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

Server operating systems

Linux
Unix
Windows

All OS with a Java VM

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

server-less

Data scheme

yes

late-bound, schema-on-read capabilities

schema-free

Flexible type definitions. Once a type is defined, it is persistent

schema-free

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

All search fields are automatically indexed

yes

via views

yes

SQL

Support of SQL

yes

SQL-like query language

yes

SQL-92 is not fully supported

APIs and other access methods

JDBC

Java API
RESTful HTTP/JSON API

HTTP REST

only for PouchDB Server
JavaScript API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

C
C#
C++
Go
Groovy
Java
PHP
Python
Scala

.Net
Groovy
Community Contributed Clients
Java
JavaScript
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

yes

View functions in JavaScript

Triggers

yes

by using the 'percolation' feature

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

with a proxy-based framework, named couchdb-lounge

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

yes

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

Hadoop integration

ES-Hadoop Connector

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency

Eventual Consistency

Synchronous doc based replication. Get by ID may show delays up to 1 sec. Configurable write consistency: one, quorum, all

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

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

Memcached and Redis integration

yes

User concepts

Access control

Access Control Lists (using HBase ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC, multi-tenancy

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.