DBMS > GBase vs. GeoMesa vs. Heroic vs. SingleStore

System Properties Comparison GBase vs. GeoMesa vs. Heroic vs. SingleStore

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Widely used RDBMS in China, including analytical, transactional, distributed transactional, and cloud-native data warehousing.

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

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

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

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	1.11
Rank	#173	Overall
	#78	Relational DBMS

Score	0.78
Rank	#214	Overall
	#4	Spatial DBMS

Score	0.13
Rank	#335	Overall
	#29	Time Series DBMS

Score	4.02
Rank	#74	Overall
	#39	Relational DBMS

Website

www.gbase.cn

www.geomesa.org

github.com/spotify/heroic

www.singlestore.com

Technical documentation

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

spotify.github.io/heroic

docs.singlestore.com

Developer

General Data Technology Co., Ltd.

CCRi and others

Spotify

SingleStore Inc.

Initial release

2004

2014

2013

Current release

GBase 8a, GBase 8s, GBase 8c

5.0.1, July 2024

8.5, January 2024

License

Commercial or Open Source

commercial

Open Source

Apache License 2.0

Open Source

Apache 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

C, Java, Python

Scala

Java

C++, Go

Server operating systems

Linux

64 bit version required

Data scheme

yes

schema-free

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

via Elasticsearch

yes

SQL

Support of SQL

Standard with numerous extensions

yes

but no triggers and foreign keys

APIs and other access methods

ADO.NET
C API
JDBC
ODBC

HQL (Heroic Query Language, a JSON-based language)
HTTP API

Cluster Management API

as HTTP Rest and CLI
HTTP API
JDBC
MongoDB API
ODBC

Supported programming languages

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

Server-side scripts

Stored procedures

user defined functions

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning (by range, list and hash) and vertical partitioning

depending on storage layer

Sharding

hash partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

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

Immediate Consistency

depending on storage layer

Eventual Consistency
Immediate Consistency

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

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

SingleStore Partners With Snowflake to Help Users Build Faster, More Efficient Real Time AI Applications
19 September 2024, Business Wire

Third time was the charm for SingleStore in the cloud, CEO says
8 July 2024, The Register

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

provided by Google News

Share this page