DBMS > Elasticsearch vs. GeoMesa vs. Machbase Neo vs. Microsoft SQL Server

System Properties Comparison Elasticsearch vs. GeoMesa vs. Machbase Neo vs. Microsoft SQL Server

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A distributed, RESTful modern search and analytics engine based on Apache Lucene

Elasticsearch lets you perform and combine many types of searches such as structured, unstructured, geo, and metric

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

TimeSeries DBMS for AIoT and BigData

Microsofts flagship relational DBMS

Primary database model

Secondary database models

Document store
Spatial DBMS
Vector DBMS

Document store
Graph DBMS
Spatial DBMS

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

Score	135.35
Rank	#7	Overall
	#1	Search engines

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	0.12
Rank	#339	Overall
	#30	Time Series DBMS

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Website

www.elastic.co/elasticsearch

www.geomesa.org

machbase.com

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

Technical documentation

www.elastic.co/guide/en/elasticsearch/reference/current/index.html

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

machbase.com/dbms

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

Developer

Elastic

CCRi and others

Machbase

Microsoft

Initial release

2010

2014

2013

1989

Current release

8.6, January 2023

4.0.5, February 2024

V8.0, August 2023

SQL Server 2022, November 2022

License

Commercial or Open Source

Open Source

Elastic License

Open Source

Apache License 2.0

commercial

free test version available

commercial

restricted free version is 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

Java

Scala

C++

Server operating systems

All OS with a Java VM

Linux
macOS
Windows

Linux
Windows

Data scheme

schema-free

Flexible type definitions. Once a type is defined, it is persistent

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

All search fields are automatically indexed

yes

SQL

Support of SQL

SQL-like query language

yes

APIs and other access methods

Java API
RESTful HTTP/JSON API

gRPC
HTTP REST
JDBC
MQTT (Message Queue Telemetry Transport)
ODBC

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

Supported programming languages

.Net
Groovy
Community Contributed Clients
Java
JavaScript
Perl
PHP
Python
Ruby

C
C#
C++
Go
Java
JavaScript
PHP

via ODBC
Python
R

via ODBC
Scala

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

Server-side scripts

Stored procedures

yes

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

Triggers

yes

by using the 'percolation' feature

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

depending on storage layer

Sharding

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

Replication methods

Methods for redundantly storing data on multiple nodes

yes

depending on storage layer

selectable replication factor

yes, but depending on the SQL-Server Edition

MapReduce

Offers an API for user-defined Map/Reduce methods

ES-Hadoop Connector

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Synchronous doc based replication. Get by ID may show delays up to 1 sec. Configurable write consistency: one, quorum, all

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

In-memory capabilities

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

Memcached and Redis integration

depending on storage layer

yes

volatile and lookup table

yes

User concepts

Access control

yes

depending on the DBMS used for storage

simple password-based access control

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.