DBMS > Machbase Neo vs. Newts vs. Quasardb vs. SQLite vs. Sqrrl

System Properties Comparison Machbase Neo vs. Newts vs. Quasardb vs. SQLite vs. Sqrrl

Editorial information provided by DB-Engines

Name

Sqrrl has been acquired by Amazon and became a part of Amazon Web Services. It has been removed from the DB-Engines ranking.

Description

TimeSeries DBMS for AIoT and BigData

Time Series DBMS based on Cassandra

Distributed, high-performance timeseries database

Widely used embeddable, in-process RDBMS

Adaptable, secure NoSQL built on Apache Accumulo

Primary database model

Time Series DBMS

Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

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

Score	0.12
Rank	#339	Overall
	#30	Time Series DBMS

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

machbase.com

opennms.github.io/newts

quasar.ai

www.sqlite.org

sqrrl.com

Technical documentation

machbase.com/dbms

github.com/OpenNMS/newts/wiki

doc.quasar.ai/master

www.sqlite.org/docs.html

Developer

Machbase

OpenNMS Group

quasardb

Dwayne Richard Hipp

Amazon

originally Sqrrl Data, Inc.

Initial release

2013

2014

2009

2000

2012

Current release

V8.0, August 2023

3.14.1, January 2024

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

commercial

free test version available

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

commercial

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++

Java

Server operating systems

Linux
macOS
Windows

Linux
OS X
Windows

BSD
Linux
OS X
Windows

server-less

Linux

Data scheme

yes

schema-free

yes

dynamic column types

schema-free

Typing

predefined data types such as float or date

yes

integer and binary

yes

not rigid because of 'dynamic typing' concept.

yes

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

with tags

yes

SQL

Support of SQL

SQL-like query language

yes

SQL-92 is not fully supported

APIs and other access methods

gRPC
HTTP REST
JDBC
MQTT (Message Queue Telemetry Transport)
ODBC

HTTP REST
Java API

HTTP API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Accumulo Shell
Java API
JDBC
ODBC
RESTful HTTP API
Thrift

Supported programming languages

C
C#
C++
Go
Java
JavaScript
PHP

via ODBC
Python
R

via ODBC
Scala

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

Actionscript
C

using GLib
C#
C++
Cocoa
Delphi
Erlang
Go
Haskell
Java
JavaScript
OCaml
Perl
PHP
Python
Ruby
Smalltalk

Server-side scripts

Stored procedures

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

based on Cassandra

Sharding

consistent hashing

none

Sharding

making use of Hadoop

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

based on Cassandra

Source-replica replication with selectable replication factor

none

selectable replication factor

making use of Hadoop

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Immediate Consistency

Document store kept consistent with combination of global timestamping, row-level transactions, and server-side consistency resolution.

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Atomic updates per row, document, or graph entity

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

yes

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.

yes

volatile and lookup table

yes

Transient mode

yes

User concepts

Access control

simple password-based access control

Cryptographically strong user authentication and audit trail

Cell-level Security, Data-Centric Security, Role-Based Access Control (RBAC), Attribute-Based Access Control (ABAC)

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.