DBMS > GeoMesa vs. jBASE vs. RDF4J vs. Solr

System Properties Comparison GeoMesa vs. jBASE vs. RDF4J vs. Solr

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.

A robust multi-value DBMS comprising development tools and middleware

RDF4J is a Java framework for processing RDF data, supporting both memory-based and a disk-based storage.

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

Primary database model

Secondary database models

Spatial DBMS

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

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	1.41
Rank	#159	Overall
	#3	Multivalue DBMS

Score	0.69
Rank	#230	Overall
	#9	RDF stores

Score	42.91
Rank	#24	Overall
	#3	Search engines

Website

www.geomesa.org

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-jbase

rdf4j.org

solr.apache.org

Technical documentation

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

docs.rocketsoftware.com/bundle?labelkey=jbase_5.9

rdf4j.org/documentation

solr.apache.org/resources.html

Developer

CCRi and others

Rocket Software (formerly Zumasys)

Since 2016 officially forked into an Eclipse project, former developer was Aduna Software.

Apache Software Foundation

Initial release

2014

1991

2004

2006

Current release

4.0.5, February 2024

5.7

9.5.0, February 2024

License

Commercial or Open Source

Open Source

Apache License 2.0

commercial

Open Source

Eclipse Distribution License (EDL), v1.0.

Open Source

Apache Version 2

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

Java

Server operating systems

AIX
Linux
Windows

Linux
OS X
Unix
Windows

All OS with a Java VM

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

Data scheme

yes

schema-free

yes

RDF Schemas

yes

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

Typing

predefined data types such as float or date

yes

optional

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

Embedded SQL for jBASE in BASIC

Solr Parallel SQL Interface

APIs and other access methods

JDBC
ODBC
Proprietary protocol
RESTful HTTP API
SOAP-based API

Java API
RIO

RDF Input/Output
Sail API
SeRQL

Sesame RDF Query Language
Sesame REST HTTP Protocol
SPARQL

Java API
RESTful HTTP/JSON API

Supported programming languages

.Net
Basic
Jabbascript
Java

Java
PHP
Python

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

Server-side scripts

Stored procedures

yes

Java plugins

Triggers

yes

User configurable commands triggered on index changes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

yes

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

Transaction concepts

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

ACID

Isolation support depends on the API used

optimistic locking

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

in-memory storage is supported as well

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

User concepts

Access control

yes

depending on the DBMS used for storage

Access rights can be defined down to the item level

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.

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

Temenos signs first customer in India
24 August 2009, Finextra

provided by Google News

GraphDB Goes Open Source
27 January 2020, iProgrammer

Ontotext's GraphDB 8.10 Makes Knowledge Graph Experience Faster and Richer
13 June 2019, Markets Insider

provided by Google News

(SOLR) Technical Pivots with Risk Controls
28 April 2024, Stock Traders Daily

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

Best Practices from Rackspace for Modernizing a Legacy HBase/Solr Architecture Using AWS Services | Amazon Web ...
9 October 2023, AWS Blog

SOLR hosts teach-in of labor movements at Northwestern
28 January 2024, Daily Northwestern

Top 5 stock gainers and losers: SOLR.V, GRSL.V, ANON.C
21 November 2023, Equity.Guru

provided by Google News

Share this page