DBMS > GeoMesa vs. Hyprcubd vs. Microsoft Azure AI Search vs. Microsoft SQL Server vs. Sphinx

System Properties Comparison GeoMesa vs. Hyprcubd vs. Microsoft Azure AI Search vs. Microsoft SQL Server vs. Sphinx

Editorial information provided by DB-Engines

Name

Hyprcubd seems to be discontinued. Therefore it is excluded from the DB-Engines ranking.

Description

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

Serverless Time Series DBMS

Search-as-a-service for web and mobile app development

Microsofts flagship relational DBMS

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

Primary database model

Secondary database models

Vector DBMS

Document store
Graph DBMS
Spatial DBMS

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

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	5.59
Rank	#63	Overall
	#7	Search engines

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	5.98
Rank	#56	Overall
	#5	Search engines

Website

www.geomesa.org

hyprcubd.com (offline)

azure.microsoft.com/en-us/services/search

www.microsoft.com/en-us/sql-server

sphinxsearch.com

Technical documentation

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

learn.microsoft.com/en-us/azure/search

learn.microsoft.com/en-US/sql/sql-server

sphinxsearch.com/docs

Developer

CCRi and others

Hyprcubd, Inc.

Microsoft

Sphinx Technologies Inc.

Initial release

2014

2015

1989

2001

Current release

4.0.5, February 2024

SQL Server 2022, November 2022

3.5.1, February 2023

License

Commercial or Open Source

Open Source

Apache License 2.0

commercial

restricted free version is available

Open Source

GPL version 2, commercial licence available

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

Scala

C++

Server operating systems

hosted

Linux
Windows

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Data scheme

yes

Typing

predefined data types such as float or date

yes

time, int, uint, float, string

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

full-text index on all search fields

SQL

Support of SQL

SQL-like query language

yes

SQL-like query language (SphinxQL)

APIs and other access methods

gRPC (https)

RESTful HTTP API

ADO.NET
JDBC
ODBC
OLE DB
Tabular Data Stream (TDS)

Proprietary protocol

Supported programming languages

C#
Java
JavaScript
Python

C#
C++
Delphi
Go
Java
JavaScript (Node.js)
PHP
Python
R
Ruby
Visual Basic

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

Server-side scripts

Stored procedures

Transact SQL, .NET languages, R, Python and (with SQL Server 2019) Java

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Sharding

Implicit feature of the cloud service

tables can be distributed across several files (horizontal partitioning); sharding through federation

Sharding

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

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

yes

Implicit feature of the cloud service

yes, but depending on the SQL-Server Edition

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

Eventual Consistency

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.

In-memory capabilities

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

depending on storage layer

yes

User concepts

Access control

yes

depending on the DBMS used for storage

token access

yes

using Azure authentication

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.