DBMS > AlaSQL vs. GeoSpock vs. Oracle Rdb vs. Sphinx vs. SQLite

System Properties Comparison AlaSQL vs. GeoSpock vs. Oracle Rdb vs. Sphinx vs. SQLite

Editorial information provided by DB-Engines

Name

GeoSpock seems to be discontinued. Therefore it will be excluded from the DB-Engines ranking.

Description

JavaScript DBMS library

Spatial and temporal data processing engine for extreme data scale

Open source search engine for searching in data from different sources, e.g. relational databases

Widely used embeddable, in-process RDBMS

Primary database model

Document store
Relational DBMS

Relational DBMS

Search engine

Relational DBMS

Secondary database models

Time Series DBMS

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

Score	0.49
Rank	#259	Overall
	#40	Document stores
	#120	Relational DBMS

Score	1.08
Rank	#187	Overall
	#85	Relational DBMS

Score	6.03
Rank	#60	Overall
	#6	Search engines

Score	116.01
Rank	#10	Overall
	#7	Relational DBMS

Website

alasql.org

geospock.com

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

sphinxsearch.com

www.sqlite.org

Technical documentation

github.com/AlaSQL/alasql

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

sphinxsearch.com/docs

www.sqlite.org/docs.html

Developer

Andrey Gershun & Mathias R. Wulff

GeoSpock

Oracle, originally developed by Digital Equipment Corporation (DEC)

Sphinx Technologies Inc.

Dwayne Richard Hipp

Initial release

2014

1984

2001

2000

Current release

2.0, September 2019

7.4.1.1, 2021

3.5.1, February 2023

3.45.2 (12 March 2024), March 2024

License

Commercial or Open Source

Open Source

MIT-License

commercial

Open Source

GPL version 2, commercial licence available

Open Source

Public Domain

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

JavaScript

Java, Javascript

C++

Server operating systems

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

hosted

HP Open VMS

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

server-less

Data scheme

schema-free

yes

Flexible Schema (defined schema, partial schema, 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

temporal, categorical

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.

ANSI SQL for query only (using Presto)

yes

SQL-like query language (SphinxQL)

yes

SQL-92 is not fully supported

APIs and other access methods

JavaScript API

JDBC

Proprietary protocol

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

JavaScript

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

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

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Automatic sharding

Sharding

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

none

Replication methods

Methods for redundantly storing data on multiple nodes

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

yes

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

Access rights for users can be defined per table

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.