DBMS > PostGIS vs. Riak TS vs. searchxml vs. Sphinx

System Properties Comparison PostGIS vs. Riak TS vs. searchxml vs. Sphinx

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Spatial extension of PostgreSQL

Riak TS is a distributed NoSQL database optimized for time series data and based on Riak KV

DBMS for structured and unstructured content wrapped with an application server

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

Primary database model

Spatial DBMS

Time Series DBMS

Native XML DBMS
Search engine

Search engine

Secondary database models

Relational DBMS

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

Score	21.72
Rank	#29	Overall
	#1	Spatial DBMS

Score	0.28
Rank	#307	Overall
	#27	Time Series DBMS

Score	0.03
Rank	#390	Overall
	#7	Native XML DBMS
	#24	Search engines

Score	5.95
Rank	#55	Overall
	#5	Search engines

Website

postgis.net

www.searchxml.net/category/products

sphinxsearch.com

Technical documentation

postgis.net/documentation

www.tiot.jp/riak-docs/riak/ts/latest

www.searchxml.net/support/handouts

sphinxsearch.com/docs

Developer

Open Source, formerly Basho Technologies

informationpartners gmbh

Sphinx Technologies Inc.

Initial release

2005

2015

2001

Current release

3.4.2, February 2024

3.0.0, September 2022

1.0

3.5.1, February 2023

License

Commercial or Open Source

Open Source

GPL v2.0

Open Source

commercial

Open Source

GPL version 2, commercial licence available

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

Erlang

C++

Server operating systems

Linux
OS X

Windows

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

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.

yes

Secondary indexes

yes

restricted

yes

full-text index on all search fields

SQL

Support of SQL

yes

yes, limited

SQL-like query language (SphinxQL)

APIs and other access methods

HTTP API
Native Erlang Interface

RESTful HTTP API
WebDAV
XQuery
XSLT

Proprietary protocol

Supported programming languages

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

C++

most other programming languages supported via APIs

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

Server-side scripts

Stored procedures

user defined functions

Erlang

yes

on the application server

Triggers

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

yes

based on PostgreSQL

Sharding

none

Sharding

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

Replication methods

Methods for redundantly storing data on multiple nodes

yes

based on PostgreSQL

selectable replication factor

yes

sychronisation to multiple collections

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

links between datasets can be stored

Transaction concepts

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

ACID

multiple readers, single writer

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

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

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

User concepts

Access control

yes

based on PostgreSQL

Domain, group and role-based access control at the document level and for application services

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

The DB-Engines ranking includes now search engines
4 February 2013, Paul Andlinger

show all

Recent citations in the news

New Basho Data Platform Provides Operational Simplicity for Enterprise Big Data Applications
7 June 2015, insideBIGDATA

Best open source databases for IoT applications
26 May 2017, Open Source For You

provided by Google News

Switching From Sphinx to MkDocs Documentation — What Did I Gain and Lose
2 February 2024, Towards Data Science

5 Powerful Alternatives to Elasticsearch
25 April 2024, Insider Monkey

Manticore is a Faster Alternative to Elasticsearch in C++
25 July 2022, hackernoon.com

Royal Mail stamp prices could rise, warns Czech Sphinx
3 June 2024, Proactive Investors UK

Perplexity AI: From Its Use To Operation, Everything You Need To Know About Google's Newest Challenger
11 January 2024, Free Press Journal

provided by Google News

Share this page