DBMS > Sphinx vs. SQLite vs. TerminusDB vs. Ultipa vs. VelocityDB

System Properties Comparison Sphinx vs. SQLite vs. TerminusDB vs. Ultipa vs. VelocityDB

Editorial information provided by DB-Engines

Name

Description

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

Widely used embeddable, in-process RDBMS

Scalable Graph Database platform making enterprise data available by exploiting inferred entities and relationships

High performance Graph DBMS supporting HTAP high availability cluster deployment

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

Primary database model

Search engine

Relational DBMS

Graph DBMS

Graph DBMS
Object oriented DBMS

Secondary database models

Document store
RDF store

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

Score	5.95
Rank	#55	Overall
	#5	Search engines

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Score	0.23
Rank	#316	Overall
	#27	Graph DBMS

Score	0.19
Rank	#330	Overall
	#30	Graph DBMS

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

Website

Technical documentation

sphinxsearch.com/docs

www.sqlite.org/docs.html

terminusdb.github.io/terminusdb/#

www.ultipa.com/document

velocitydb.com/UserGuide

Developer

Sphinx Technologies Inc.

Dwayne Richard Hipp

DataChemist Ltd.

Ultipa

VelocityDB Inc

Initial release

2001

2000

2018

2019

2011

Current release

3.5.1, February 2023

3.46.0 (23 May 2024), May 2024

11.0.0, January 2023

7.x

License

Commercial or Open Source

Open Source

GPL version 2, commercial licence available

Open Source

Public Domain

Open Source

GPL V3

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

C++

Prolog, Rust

Server operating systems

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

server-less

Linux

Any that supports .NET

Data scheme

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

full-text index on all search fields

yes

SQL

Support of SQL

SQL-like query language (SphinxQL)

yes

SQL-92 is not fully supported

SQL-like query language (WOQL)

APIs and other access methods

Proprietary protocol

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

RESTful HTTP API

.Net

Supported programming languages

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

JavaScript
Python

C++
Go
Java
JavaScript (Node.js)
Python

.Net

Server-side scripts

Stored procedures

yes

Triggers

yes

Callbacks are triggered when data changes

Partitioning methods

Methods for storing different data on different nodes

Sharding

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

none

Graph Partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

Journaling Streams

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

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

yes

Durability

Support for making data persistent

yes

The original contents of fields are not stored in the Sphinx index.

yes

in-memory journaling

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

Role-based access control

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.