DBMS > GeoMesa vs. RavenDB vs. STSdb vs. SWC-DB vs. Transbase

System Properties Comparison GeoMesa vs. RavenDB vs. STSdb vs. SWC-DB vs. Transbase

Editorial information provided by DB-Engines

Name

Description

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

Open Source Operational and Transactional Enterprise NoSQL Document Database

Key-Value Store with special method for indexing

optimized for high performance using a special indexing method

A high performance, scalable Wide Column DBMS

A resource-optimized, high-performance, universally applicable RDBMS

Primary database model

Secondary database models

Graph DBMS
Spatial DBMS
Time Series DBMS

Time Series DBMS

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

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	2.92
Rank	#101	Overall
	#18	Document stores

Score	0.04
Rank	#360	Overall
	#52	Key-value stores

Score	0.01
Rank	#376	Overall
	#13	Wide column stores

Score	0.11
Rank	#341	Overall
	#150	Relational DBMS

Website

www.geomesa.org

ravendb.net

github.com/STSSoft/STSdb4

github.com/kashirin-alex/swc-db
www.swcdb.org

www.transaction.de/en/products/transbase.html

Technical documentation

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

ravendb.net/docs

www.transaction.de/en/products/transbase/features.html

Developer

CCRi and others

Hibernating Rhinos

STS Soft SC

Alex Kashirin

Transaction Software GmbH

Initial release

2014

2010

2011

2020

1987

Current release

5.0.0, May 2024

5.4, July 2022

4.0.8, September 2015

0.5, April 2021

Transbase 8.3, 2022

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

AGPL version 3, commercial license available

Open Source

GPLv2, commercial license available

Open Source

GPL V3

commercial

free development license

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++

C and C++

Server operating systems

Linux
macOS
Raspberry Pi
Windows

Windows

Linux

FreeBSD
Linux
macOS
Solaris
Windows

Data scheme

yes

schema-free

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

primitive types and user defined types (classes)

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.

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language (RQL)

SQL-like query language

yes

APIs and other access methods

.NET Client API
F# Client API
Go Client API
Java Client API
NodeJS Client API
PHP Client API
Python Client API
RESTful HTTP API

.NET Client API

Proprietary protocol
Thrift

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

.Net
C#
F#
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

C#
Java

C++

C
C#
C++
Java
JavaScript
Kotlin
Objective-C
PHP
Python

Server-side scripts

Stored procedures

yes

Triggers

yes

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

Multi-source replication

none

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

depending on storage layer

Default ACID transactions on the local node (eventually consistent across the cluster). Atomic operations with cluster-wide ACID transactions. Eventual consistency for indexes and full-text search indexes.

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID, Cluster-wide transaction available

yes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

depending on storage layer

User concepts

Access control

yes

depending on the DBMS used for storage

Authorization levels configured per client per database

fine grained access rights according to SQL-standard

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

Recent citations in the news

RavenDB Launches Version 6.0 Lightning Fast Queries, Data Integrations, Corax Indexing Engine, and Sharding
3 October 2023, PR Newswire

RavenDB Welcomes David Baruc as Chief Revenue Officer: Seasoned Tech Leader to Drive Global Sales and ...
13 June 2023, PR Newswire

Install the NoSQL RavenDB Data System
14 May 2021, The New Stack

RavenDB Adds Graph Queries
15 May 2019, Datanami

How I Created a RavenDB Python Client
23 September 2016, Visual Studio Magazine

provided by Google News

2022 All O-Zone Football Team
17 December 2022, Ozarks Sports Zone

provided by Google News

Share this page