DBMS > Elasticsearch vs. Newts vs. Quasardb vs. SQLite

System Properties Comparison Elasticsearch vs. Newts vs. Quasardb vs. SQLite

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

Time Series DBMS based on Cassandra

Distributed, high-performance timeseries database

Widely used embeddable, in-process RDBMS

Primary database model

Search engine

Time Series DBMS

Relational DBMS

Secondary database models

Document store
Spatial DBMS
Vector DBMS

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

Score	135.35
Rank	#7	Overall
	#1	Search engines

Score	0.00
Rank	#383	Overall
	#41	Time Series DBMS

Score	0.14
Rank	#332	Overall
	#29	Time Series DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

www.elastic.co/elasticsearch

opennms.github.io/newts

quasar.ai

www.sqlite.org

Technical documentation

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

github.com/OpenNMS/newts/wiki

doc.quasar.ai/master

www.sqlite.org/docs.html

Developer

Elastic

OpenNMS Group

quasardb

Dwayne Richard Hipp

Initial release

2010

2014

2009

2000

Current release

8.6, January 2023

3.14.1, January 2024

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

Open Source

Elastic License

Open Source

Apache 2.0

commercial

Free community edition, Non-profit organizations and non-commercial usage are eligible for free licenses

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

C++

Server operating systems

All OS with a Java VM

Linux
OS X
Windows

BSD
Linux
OS X
Windows

server-less

Data scheme

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

integer and binary

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

with tags

yes

SQL

Support of SQL

SQL-like query language

yes

SQL-92 is not fully supported

APIs and other access methods

Java API
RESTful HTTP/JSON API

HTTP REST
Java API

HTTP API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

.Net
Groovy
Community Contributed Clients
Java
JavaScript
Perl
PHP
Python
Ruby

Java

.Net
C
C#
C++
Go
Java
JavaScript (Node.js)
PHP
Python
R

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

Triggers

yes

by using the 'percolation' feature

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

based on Cassandra

Sharding

consistent hashing

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor

based on Cassandra

Source-replica replication with selectable replication factor

none

MapReduce

Offers an API for user-defined Map/Reduce methods

ES-Hadoop Connector

with Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

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

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Immediate 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 LevelDB

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

Memcached and Redis integration

yes

Transient mode

yes

User concepts

Access control

Cryptographically strong user authentication and audit trail

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.