DBMS > GeoMesa vs. Lovefield vs. SAP HANA vs. SiriDB vs. Solr

System Properties Comparison GeoMesa vs. Lovefield vs. SAP HANA vs. SiriDB vs. Solr

Editorial information provided by DB-Engines

Name

Description

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

Embeddable relational database for web apps written in pure JavaScript

In-memory, column based data store. Available as appliance or cloud service

Open Source Time Series DBMS

A widely used distributed, scalable search engine based on Apache Lucene

Primary database model

Secondary database models

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

Spatial DBMS

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

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	0.33
Rank	#286	Overall
	#131	Relational DBMS

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Score	0.07
Rank	#378	Overall
	#42	Time Series DBMS

Score	41.02
Rank	#24	Overall
	#3	Search engines

Website

www.geomesa.org

google.github.io/lovefield

www.sap.com/products/hana.html

siridb.com

solr.apache.org

Technical documentation

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

github.com/google/lovefield/blob/master/docs/spec_index.md

help.sap.com/hana

docs.siridb.com

solr.apache.org/resources.html

Developer

CCRi and others

Google

SAP

Cesbit

Apache Software Foundation

Initial release

2014

2010

2017

2006

Current release

5.0.0, May 2024

2.1.12, February 2017

2.0 SPS07 (April 4, 2023), April 2023

9.6.1, May 2024

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

Apache 2.0

commercial

Open Source

MIT License

Open Source

Apache Version 2

Cloud-based only

Only available as a cloud service

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Scala

JavaScript

Java

Server operating systems

server-less, requires a JavaScript environment (browser, Node.js)

tested with Chrome, Firefox, IE, Safari

Appliance or cloud-service

Linux

All OS with a Java VM

runs as a servlet in servlet container (e.g. Tomcat, Jetty is included)

Data scheme

yes

Dynamic Fields enables on-the-fly addition of new fields

Typing

predefined data types such as float or date

yes

Numeric data

yes

supports customizable data types and automatic typing

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

SQL

Support of SQL

SQL-like query language

via JavaScript builder pattern

yes

Solr Parallel SQL Interface

APIs and other access methods

JDBC
ODBC

HTTP API

Java API
RESTful HTTP/JSON API

Supported programming languages

JavaScript

C
C++
Go
Java
JavaScript (Node.js)
PHP
Python
R

.Net
Erlang
Java
JavaScript
any language that supports sockets and either XML or JSON
Perl
PHP
Python
Ruby
Scala

Server-side scripts

Stored procedures

SQLScript, R

Java plugins

Triggers

Using read-only observers

yes

User configurable commands triggered on index changes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

none

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

spark-solr: github.com/lucidworks/spark-solr and streaming expressions to reduce

Consistency concepts

Methods to ensure consistency in a distributed system

depending on storage layer

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

optimistic locking

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes, by using IndexedDB or the cloud service Firebase Realtime Database

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 MemoryDB

yes

User concepts

Access control

yes

depending on the DBMS used for storage

yes

simple rights management via user accounts

yes

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.