DBMS > GeoMesa vs. Lovefield vs. SiriDB vs. Solr vs. YottaDB

System Properties Comparison GeoMesa vs. Lovefield vs. SiriDB vs. Solr vs. YottaDB

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

Open Source Time Series DBMS

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

A fast and solid embedded Key-value store

Primary database model

Secondary database models

Spatial DBMS

Relational DBMS

using the Octo plugin

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	0.07
Rank	#378	Overall
	#42	Time Series DBMS

Score	41.02
Rank	#24	Overall
	#3	Search engines

Score	0.28
Rank	#306	Overall
	#44	Key-value stores

Website

www.geomesa.org

google.github.io/lovefield

siridb.com

solr.apache.org

yottadb.com

Technical documentation

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

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

docs.siridb.com

solr.apache.org/resources.html

yottadb.com/resources/documentation

Developer

CCRi and others

Google

Cesbit

Apache Software Foundation

YottaDB, LLC

Initial release

2014

2017

2006

2001

Current release

5.0.0, May 2024

2.1.12, February 2017

9.6.1, May 2024

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

Apache 2.0

Open Source

MIT License

Open Source

Apache Version 2

Open Source

AGPL 3.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

JavaScript

Java

Server operating systems

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

tested with Chrome, Firefox, IE, Safari

Linux

All OS with a Java VM

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

Docker
Linux

Data scheme

yes

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

schema-free

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

Solr Parallel SQL Interface

by using the Octo plugin

APIs and other access methods

HTTP API

Java API
RESTful HTTP/JSON API

PostgreSQL wire protocol

using the Octo plugin
Proprietary protocol

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

C
Go
JavaScript (Node.js)
Lua
M
Perl
Python
Rust

Server-side scripts

Stored procedures

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

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

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

simple rights management via user accounts

yes

Users and groups based on OS-security mechanisms

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

Elasticsearch replaced Solr as the most popular search engine
12 January 2016, Paul Andlinger

Enterprise Search Engines almost double their popularity in the last 12 months
2 July 2014, Paul Andlinger

The DB-Engines ranking includes now search engines
4 February 2013, Paul Andlinger

show all

Recent citations in the news

Kagiso interactive shares: all eyes on android at google I/O
11 May 2015, WhaTech

provided by Google News

SOLR-led walkout demands better conditions for Compass workers
27 February 2024, Daily Northwestern

Solr Network Launches Groundbreaking Solana Token Creator
28 May 2024, AccessWire

(SOLR) Technical Data
17 May 2024, news.stocktradersdaily.com

Have Insiders Been Buying Solar Alliance Energy Inc. (CVE:SOLR) Shares?
27 May 2024, Yahoo Movies UK

Solana Token Creator by Solr Network Becomes the Fastest-Growing Platform on Solana
16 May 2024, WICZ

provided by Google News

Share this page