DBMS > GeoMesa vs. Sphinx vs. Stardog vs. Tkrzw

System Properties Comparison GeoMesa vs. Sphinx vs. Stardog vs. Tkrzw

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

Enterprise Knowledge Graph platform and graph DBMS with high availability, high performance reasoning, and virtualization

A concept of libraries, allowing an application program to store and query key-value pairs in a file. Successor of Tokyo Cabinet and Kyoto Cabinet

Primary database model

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	2.07
Rank	#122	Overall
	#11	Graph DBMS
	#6	RDF stores

Score	0.07
Rank	#372	Overall
	#57	Key-value stores

Website

Technical documentation

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

sphinxsearch.com/docs

docs.stardog.com

Developer

CCRi and others

Sphinx Technologies Inc.

Stardog-Union

Mikio Hirabayashi

Initial release

2014

2001

2010

2020

Current release

5.0.0, May 2024

3.5.1, February 2023

7.3.0, May 2020

0.9.3, August 2020

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

GPL version 2, commercial licence available

commercial

60-day fully-featured trial license; 1-year fully-featured non-commercial use license for academics/students

Open Source

Apache Version 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++

Java

C++

Server operating systems

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Linux
macOS
Windows

Linux
macOS

Data scheme

yes

schema-free and OWL/RDFS-schema support

schema-free

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.

Import/export of XML data possible

Secondary indexes

yes

full-text index on all search fields

yes

supports real-time indexing in full-text and geospatial

SQL

Support of SQL

SQL-like query language (SphinxQL)

Yes, compatible with all major SQL variants through dedicated BI/SQL Server

APIs and other access methods

Proprietary protocol

GraphQL query language
HTTP API
Jena RDF API
OWL
RDF4J API
Sesame REST HTTP Protocol
SNARL
SPARQL
Spring Data
Stardog Studio
TinkerPop 3

Supported programming languages

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

.Net
Clojure
Groovy
Java
JavaScript
Python
Ruby

C++
Java
Python
Ruby

Server-side scripts

Stored procedures

user defined functions and aggregates, HTTP Server extensions in Java

Triggers

yes

via event handlers

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

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

none

Multi-source replication in HA-Cluster

none

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 in HA-Cluster

Immediate Consistency

Foreign keys

Referential integrity

yes

relationships in graphs

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

yes

using specific database classes

User concepts

Access control

yes

depending on the DBMS used for storage

Access rights for users and roles

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

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