DBMS > GeoMesa vs. Sphinx vs. STSdb vs. TimescaleDB

System Properties Comparison GeoMesa vs. Sphinx vs. STSdb vs. TimescaleDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

GeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.

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

Key-Value Store with special method for indexing

optimized for high performance using a special indexing method

A time series DBMS optimized for fast ingest and complex queries, based on PostgreSQL

Primary database model

Secondary database models

Relational DBMS

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

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	5.95
Rank	#55	Overall
	#5	Search engines

Score	0.10
Rank	#357	Overall
	#51	Key-value stores

Score	4.46
Rank	#71	Overall
	#5	Time Series DBMS

Website

www.geomesa.org

sphinxsearch.com

github.com/STSSoft/STSdb4

www.timescale.com

Technical documentation

www.geomesa.org/documentation/stable/user/index.html

sphinxsearch.com/docs

docs.timescale.com

Developer

CCRi and others

Sphinx Technologies Inc.

STS Soft SC

Timescale

Initial release

2014

2001

2011

2017

Current release

5.0.0, May 2024

3.5.1, February 2023

4.0.8, September 2015

2.15.0, May 2024

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

GPL version 2, commercial licence available

Open Source

GPLv2, commercial license available

Open Source

Apache 2.0

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

Scala

C++

Server operating systems

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Windows

Linux
OS X
Windows

Data scheme

yes

Typing

predefined data types such as float or date

yes

primitive types and user defined types (classes)

numerics, strings, booleans, arrays, JSON blobs, geospatial dimensions, currencies, binary data, other complex data types

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

full-text index on all search fields

yes

SQL

Support of SQL

SQL-like query language (SphinxQL)

yes

full PostgreSQL SQL syntax

APIs and other access methods

Proprietary protocol

.NET Client API

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

Supported programming languages

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

C#
Java

.Net
C
C++
Delphi
Java

JDBC
JavaScript
Perl
PHP
Python
R
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

user defined functions, PL/pgSQL, PL/Tcl, PL/Perl, PL/Python, PL/Java, PL/PHP, PL/R, PL/Ruby, PL/Scheme, PL/Unix shell

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Sharding

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

none

yes, across time and space (hash partitioning) attributes

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

none

Source-replica replication with hot standby and reads on replicas

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

depending on storage layer

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

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.

depending on storage layer

User concepts

Access control

yes

depending on the DBMS used for storage

fine grained access rights according to SQL-standard

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

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

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

Czech billionaire 'very serious' about bid for Royal Mail
19 April 2024, The Telegraph

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

The Pirate Bay was recently down for over a week due to a DDoS attack
29 October 2019, The Hacker News

provided by Google News

TimescaleDB Is a Vector Database Now, Too
25 September 2023, Datanami

Timescale Acquires PopSQL to Bring a Modern, Collaborative SQL GUI to PostgreSQL Developers
4 April 2024, PR Newswire

Power IoT and time-series workloads with TimescaleDB for Azure Database for PostgreSQL
18 March 2019, Microsoft

Timescale Valuation Rockets to Over $1B with $110M Round, Marking the Explosive Rise of Time-Series Data
22 February 2022, Business Wire

Timescale announces $15M investment and new enterprise version of TimescaleDB
29 January 2019, TechCrunch

provided by Google News

Share this page