DBMS > GeoMesa vs. jBASE vs. LeanXcale vs. SingleStore

System Properties Comparison GeoMesa vs. jBASE vs. LeanXcale vs. SingleStore

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

A highly scalable full ACID SQL database with fast NoSQL data ingestion and GIS capabilities

MySQL wire-compliant distributed RDBMS that combines an in-memory row-oriented and a disc-based column-oriented storage with patented universal storage to handle transactional and analytical workloads in one single table type

Primary database model

Spatial DBMS

Multivalue DBMS

Key-value store
Relational DBMS

Relational DBMS

Secondary database models

Document store
Spatial DBMS
Time Series DBMS
Vector DBMS

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

Score	0.78
Rank	#214	Overall
	#4	Spatial DBMS

Score	1.36
Rank	#157	Overall
	#3	Multivalue DBMS

Score	0.28
Rank	#286	Overall
	#41	Key-value stores
	#130	Relational DBMS

Score	4.02
Rank	#74	Overall
	#39	Relational DBMS

Website

www.geomesa.org

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

www.leanxcale.com

www.singlestore.com

Technical documentation

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

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

docs.singlestore.com

Developer

CCRi and others

Rocket Software (formerly Zumasys)

LeanXcale

SingleStore Inc.

Initial release

2014

1991

2015

2013

Current release

5.0.1, July 2024

5.7

8.5, January 2024

License

Commercial or Open Source

Open Source

Apache License 2.0

commercial

free developer edition 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

Scala

C++, Go

Server operating systems

AIX
Linux
Windows

Linux

64 bit version required

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

optional

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

SQL

Support of SQL

Embedded SQL for jBASE in BASIC

yes

through Apache Derby

yes

but no triggers and foreign keys

APIs and other access methods

JDBC
ODBC
Proprietary protocol
RESTful HTTP API
SOAP-based API

JDBC
Kafka Connector
ODBC
proprietary key/value interface
Spark Connector

Cluster Management API

as HTTP Rest and CLI
HTTP API
JDBC
MongoDB API
ODBC

Supported programming languages

.Net
Basic
Jabbascript
Java

C
Java
Scala

Bash
C
C#
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Sharding

hash partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

yes

Source-replica replication

stores two copies of each physical data partition on two separate nodes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

can define user-defined aggregate functions for map-reduce-style calculations

Consistency concepts

Methods to ensure consistency in a distributed system

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

yes, multi-version concurrency control (MVCC)

Durability

Support for making data persistent

yes

All updates are persistent, including those to disk-based columnstores and memory-based row stores. Transaction commits are supported via write-ahead log.

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

Fine grained access control via users, groups and roles

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

Turbocharge Your Application Development Using WebAssembly With SingleStoreDB
17 October 2022, Akmal Chaudhri, SingleStore (sponsor)

Cloud-Based Analytics With SingleStoreDB
9 June 2022, Akmal Chaudhri, SingleStore (sponsor)

SingleStore: The Increasing Momentum of Multi-Model Database Systems
14 February 2022, Akmal Chaudhri, SingleStore (sponsor)

show all

Recent citations in the news

Temenos signs first customer in India
24 August 2009, Finextra

provided by Google News

SingleStore Partners With Snowflake to Help Users Build Faster, More Efficient Real Time AI Applications
19 September 2024, businesswire.com

SingleStore CEO sees little future for purpose-built vector databases
24 January 2024, VentureBeat

Achieve near real-time analytics on Amazon DynamoDB with SingleStore
16 September 2024, AWS Blog

Building a Modern Database: Nikita Shamgunov on Postgres and Beyond
18 April 2024, Madrona Venture Group

SingleStore: We do vectors and you don’t need knowledge graphs
22 July 2024, Blocks & Files

provided by Google News

Share this page