DBMS > AlaSQL vs. Graph Engine vs. Manticore Search vs. Oracle Rdb vs. SQLite

System Properties Comparison AlaSQL vs. Graph Engine vs. Manticore Search vs. Oracle Rdb vs. SQLite

Editorial information provided by DB-Engines

Name

Description

JavaScript DBMS library

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

Multi-storage database for search, including full-text search.

Widely used embeddable, in-process RDBMS

Primary database model

Document store
Relational DBMS

Graph DBMS
Key-value store

Search engine

Relational DBMS

Secondary database models

Time Series DBMS

using the Manticore Columnar Library

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

Score	0.46
Rank	#260	Overall
	#40	Document stores
	#121	Relational DBMS

Score	0.61
Rank	#240	Overall
	#21	Graph DBMS
	#35	Key-value stores

Score	0.22
Rank	#312	Overall
	#21	Search engines

Score	1.08
Rank	#184	Overall
	#85	Relational DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

alasql.org

www.graphengine.io

manticoresearch.com

www.oracle.com/database/technologies/related/rdb.html

www.sqlite.org

Technical documentation

github.com/AlaSQL/alasql

www.graphengine.io/docs/manual

manual.manticoresearch.com

www.oracle.com/database/technologies/related/rdb-doc.html

www.sqlite.org/docs.html

Developer

Andrey Gershun & Mathias R. Wulff

Microsoft

Manticore Software

Oracle, originally developed by Digital Equipment Corporation (DEC)

Dwayne Richard Hipp

Initial release

2014

2010

2017

1984

2000

Current release

6.0, February 2023

7.4.1.1, 2021

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

Open Source

MIT-License

Open Source

MIT License

Open Source

GPL version 2

commercial

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

JavaScript

.NET and C

C++

Server operating systems

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

.NET

FreeBSD
Linux
macOS
Windows

HP Open VMS

server-less

Data scheme

schema-free

yes

Fixed schema

Flexible Schema (defined schema, partial schema, schema free)

yes

dynamic column types

Typing

predefined data types such as float or date

yes

Int, Bigint, Float, Timestamp, Bit, Int array, Bigint array, JSON, Boolean

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.

Can index from XML

Secondary indexes

yes

full-text index on all search fields

yes

SQL

Support of SQL

Close to SQL99, but no user access control, stored procedures and host language bindings.

SQL-like query language

yes

SQL-92 is not fully supported

APIs and other access methods

JavaScript API

RESTful HTTP API

Binary API
RESTful HTTP/JSON API
RESTful HTTP/SQL API
SQL over MySQL

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

JavaScript

C#
C++
F#
Visual Basic

Elixir
Go
Java
JavaScript (Node.js)
Perl
PHP
Python

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

user defined functions

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning

Sharding

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

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

Synchronous replication based on Galera library

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

only for local storage and DOM-storage

yes

isolated transactions for atomic changes and binary logging for safe writes

yes, on a single node

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

Durability

Support for making data persistent

yes

by using IndexedDB, SQL.JS or proprietary FileStorage

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

yes

The original contents of fields are not stored in the Manticore 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

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.