DBMS > GeoSpock vs. RavenDB vs. SWC-DB vs. Transbase vs. WakandaDB

System Properties Comparison GeoSpock vs. RavenDB vs. SWC-DB vs. Transbase vs. WakandaDB

Editorial information provided by DB-Engines

Name

GeoSpock seems to be discontinued. Therefore it will be excluded from the DB-Engines ranking.

Description

Spatial and temporal data processing engine for extreme data scale

Open Source Operational and Transactional Enterprise NoSQL Document Database

A high performance, scalable Wide Column DBMS

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

WakandaDB is embedded in a server that provides a REST API and a server-side javascript engine to access data

Primary database model

Secondary database models

Time Series DBMS

Graph DBMS
Spatial DBMS
Time Series DBMS

Time Series DBMS

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

Score	3.01
Rank	#101	Overall
	#17	Document stores

Score	0.01
Rank	#387	Overall
	#13	Wide column stores

Score	0.15
Rank	#337	Overall
	#147	Relational DBMS

Score	0.09
Rank	#352	Overall
	#16	Object oriented DBMS

Website

geospock.com

ravendb.net

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

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

wakanda.github.io

Technical documentation

ravendb.net/docs

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

wakanda.github.io/doc

Developer

GeoSpock

Hibernating Rhinos

Alex Kashirin

Transaction Software GmbH

Wakanda SAS

Initial release

2010

2020

1987

2012

Current release

2.0, September 2019

5.4, July 2022

0.5, April 2021

Transbase 8.3, 2022

2.7.0 (April 29, 2019), April 2019

License

Commercial or Open Source

commercial

Open Source

AGPL version 3, commercial license available

Open Source

GPL V3

commercial

free development license

Open Source

AGPLv3, extended commercial license available

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java, Javascript

C++

C and C++

C++, JavaScript

Server operating systems

hosted

Linux
macOS
Raspberry Pi
Windows

Linux

FreeBSD
Linux
macOS
Solaris
Windows

Linux
OS X
Windows

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.

Secondary indexes

temporal, categorical

yes

SQL

Support of SQL

ANSI SQL for query only (using Presto)

SQL-like query language (RQL)

SQL-like query language

yes

APIs and other access methods

JDBC

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

Proprietary protocol
Thrift

ADO.NET
JDBC
ODBC
Proprietary native API

RESTful HTTP API

Supported programming languages

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

C++

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

JavaScript

Server-side scripts

Stored procedures

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Automatic sharding

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

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

ACID

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.

User concepts

Access control

Access rights for users can be defined per table

Authorization levels configured per client per database

fine grained access rights according to SQL-standard

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

Recent citations in the news

How GeoSpock is supercharging geospatial analytics
23 February 2021, ComputerWeekly.com

GeoSpock launches Spatial Big Data Platform 2.0
4 September 2019, VanillaPlus

nChain Leads Investment Round in Extreme-scale Data Firm GeoSpock
2 October 2020, AlexaBlockchain

GeoSpock’s extreme-scale data mission in $5.4m funding boost
8 October 2020, Cambridge Independent

Smart Cities, Autonomous Vehicles, Artificial General Intelligence Robotics: Q&A with Steve Marsh, GeoSpock
16 May 2018, ExchangeWire

provided by Google News

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

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

RavenDB Adds Graph Queries
15 May 2019, Datanami

Review: NoSQL database RavenDB
20 March 2019, TechGenix

provided by Google News

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

provided by Google News

Share this page