DBMS > Amazon CloudSearch vs. Apache Phoenix vs. SQLite vs. VictoriaMetrics

System Properties Comparison Amazon CloudSearch vs. Apache Phoenix vs. SQLite vs. VictoriaMetrics

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A hosted search engine service by Amazon with the data stored in Amazons cloud

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

Widely used embeddable, in-process RDBMS

A fast, cost-effective and scalable Time Series DBMS and monitoring solution

Primary database model

Search engine

Relational DBMS

Time Series DBMS

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

Score	1.85
Rank	#137	Overall
	#12	Search engines

Score	1.97
Rank	#126	Overall
	#59	Relational DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Score	1.32
Rank	#162	Overall
	#14	Time Series DBMS

Website

aws.amazon.com/cloudsearch

phoenix.apache.org

www.sqlite.org

victoriametrics.com

Technical documentation

docs.aws.amazon.com/cloudsearch

phoenix.apache.org

www.sqlite.org/docs.html

docs.victoriametrics.com
github.com/VictoriaMetrics/VictoriaMetrics/wiki

Developer

Amazon

Apache Software Foundation

Dwayne Richard Hipp

VictoriaMetrics

Initial release

2012

2014

2000

2018

Current release

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

3.45.3 (15 April 2024), April 2024

v1.91, May 2023

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

Open Source

Public Domain

Open Source

Apache Version 2.0

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java

Server operating systems

hosted

Linux
Unix
Windows

server-less

FreeBSD
Linux
macOS
OpenBSD

Data scheme

yes

late-bound, schema-on-read capabilities

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

SQL

Support of SQL

yes

SQL-92 is not fully supported

APIs and other access methods

HTTP API

JDBC

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Graphite protocol
InfluxDB Line Protocol
OpenTSDB
Prometheus Query API
Prometheus Remote Read/Write

Supported programming languages

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

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

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

yes

automatic partitioning across Amazon Search Instance as required

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

managed transparently by AWS

Multi-source replication
Source-replica replication

none

Synchronous replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual 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

via file-system locks

yes

Durability

Support for making data persistent

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

authentication via encrypted signatures

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.