DBMS > CouchDB vs. GeoSpock vs. Sphinx vs. SQLite vs. VelocityDB

System Properties Comparison CouchDB vs. GeoSpock vs. Sphinx vs. SQLite vs. VelocityDB

Editorial information provided by DB-Engines

Name

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

Description

A native JSON - document store inspired by Lotus Notes, scalable from globally distributed server-clusters down to mobile phones.

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

A .NET Object Database that can be embedded/distributed and extended to a graph data model (VelocityGraph)

Primary database model

Graph DBMS
Object oriented DBMS

Secondary database models

Spatial DBMS

using the Geocouch extension

Time Series DBMS

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

Score	8.30
Rank	#47	Overall
	#7	Document stores

Score	5.95
Rank	#55	Overall
	#5	Search engines

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Score	0.11
Rank	#354	Overall
	#37	Graph DBMS
	#15	Object oriented DBMS

Website

geospock.com

Technical documentation

docs.couchdb.org/en/stable

sphinxsearch.com/docs

www.sqlite.org/docs.html

velocitydb.com/UserGuide

Developer

Apache Software Foundation

Apache top-level project, originally developed by Damien Katz, a former Lotus Notes developer

GeoSpock

Sphinx Technologies Inc.

Dwayne Richard Hipp

VelocityDB Inc

Initial release

2005

2001

2000

2011

Current release

3.3.3, December 2023

2.0, September 2019

3.5.1, February 2023

3.46.0 (23 May 2024), May 2024

7.x

License

Commercial or Open Source

Open Source

Apache version 2

commercial

Open Source

GPL version 2, commercial licence available

Open Source

Public Domain

commercial

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

Erlang

Java, Javascript

C++

Server operating systems

Android
BSD
Linux
OS X
Solaris
Windows

hosted

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

server-less

Any that supports .NET

Data scheme

schema-free

yes

dynamic column types

yes

Typing

predefined data types such as float or date

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

via views

temporal, categorical

yes

full-text index on all search fields

yes

SQL

Support of SQL

ANSI SQL for query only (using Presto)

SQL-like query language (SphinxQL)

yes

SQL-92 is not fully supported

APIs and other access methods

RESTful HTTP/JSON API

JDBC

Proprietary protocol

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

.Net

Supported programming languages

C
C#
ColdFusion
Erlang
Haskell
Java
JavaScript
Lisp
Lua
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
Ruby
Smalltalk

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

.Net

Server-side scripts

Stored procedures

View functions in JavaScript

Triggers

yes

Callbacks are triggered when data changes

Partitioning methods

Methods for storing different data on different nodes

Sharding

improved architecture with release 2.0

Automatic sharding

Sharding

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

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

atomic operations within a single document possible

ACID

Concurrency

Support for concurrent manipulation of data

yes

strategy: optimistic locking

yes

via file-system locks

yes

Durability

Support for making data persistent

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 database

Access rights for users can be defined per table

Based on Windows Authentication

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.