DBMS > Brytlyt vs. GeoSpock vs. RavenDB vs. SAP HANA

System Properties Comparison Brytlyt vs. GeoSpock vs. RavenDB vs. SAP HANA

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

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

Description

Scalable GPU-accelerated RDBMS for very fast analytic and streaming workloads, leveraging PostgreSQL

Spatial and temporal data processing engine for extreme data scale

Open Source Operational and Transactional Enterprise NoSQL Document Database

In-memory, column based data store. Available as appliance or cloud service

Primary database model

Relational DBMS

Document store

Relational DBMS

Secondary database models

Time Series DBMS

Graph DBMS
Spatial DBMS
Time Series DBMS

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	0.29
Rank	#288	Overall
	#131	Relational DBMS

Score	2.92
Rank	#101	Overall
	#18	Document stores

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Website

brytlyt.io

geospock.com

ravendb.net

www.sap.com/products/hana.html

Technical documentation

docs.brytlyt.io

ravendb.net/docs

help.sap.com/hana

Developer

Brytlyt

GeoSpock

Hibernating Rhinos

SAP

Initial release

2016

2010

Current release

5.0, August 2023

2.0, September 2019

5.4, July 2022

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

commercial

Open Source

AGPL version 3, commercial license available

commercial

Cloud-based only

Only available as a cloud service

yes

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

C, C++ and CUDA

Java, Javascript

Server operating systems

Linux
OS X
Windows

hosted

Linux
macOS
Raspberry Pi
Windows

Appliance or cloud-service

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

specific XML-type available, but no XML query functionality.

Secondary indexes

yes

temporal, categorical

yes

SQL

Support of SQL

yes

ANSI SQL for query only (using Presto)

SQL-like query language (RQL)

yes

APIs and other access methods

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

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

JDBC
ODBC

Supported programming languages

.Net
C
C++
Delphi
Java
Perl
Python
Tcl

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

Server-side scripts

Stored procedures

user defined functions

in PL/pgSQL

yes

SQLScript, R

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Automatic sharding

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Multi-source replication

yes

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

ACID, Cluster-wide transaction available

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.

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Access rights for users can be defined per table

Authorization levels configured per client per database

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.