DBMS > EsgynDB vs. Google Cloud Datastore vs. RDF4J vs. ReductStore vs. SwayDB

System Properties Comparison EsgynDB vs. Google Cloud Datastore vs. RDF4J vs. ReductStore vs. SwayDB

Editorial information provided by DB-Engines

Name

Description

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

RDF4J is a Java framework for processing RDF data, supporting both memory-based and a disk-based storage.

Designed to manage unstructured time-series data efficiently, providing unique features such as storing time-stamped blobs with labels, customizable data retention policies, and a straightforward FIFO quota system.

An embeddable, non-blocking, type-safe key-value store for single or multiple disks and in-memory storage

Primary database model

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

Score	0.15
Rank	#325	Overall
	#144	Relational DBMS

Score	4.13
Rank	#71	Overall
	#12	Document stores

Score	0.72
Rank	#222	Overall
	#9	RDF stores

Score	0.00
Rank	#385	Overall
	#40	Time Series DBMS

Score	0.00
Rank	#384	Overall
	#60	Key-value stores

Website

www.esgyn.cn

cloud.google.com/datastore

rdf4j.org

github.com/reductstore
www.reduct.store

swaydb.simer.au

Technical documentation

cloud.google.com/datastore/docs

rdf4j.org/documentation

www.reduct.store/docs

Developer

Esgyn

Google

Since 2016 officially forked into an Eclipse project, former developer was Aduna Software.

ReductStore LLC

Simer Plaha

Initial release

2015

2008

2004

2023

2018

Current release

1.9, March 2024

License

Commercial or Open Source

commercial

Open Source

Eclipse Distribution License (EDL), v1.0.

Open Source

Business Source License 1.1

Open Source

GNU Affero GPL V3.0

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

C++, Java

Java

C++, Rust

Scala

Server operating systems

Linux

hosted

Linux
OS X
Unix
Windows

Docker
Linux
macOS
Windows

Data scheme

yes

schema-free

yes

RDF Schemas

schema-free

Typing

predefined data types such as float or date

yes

yes, details here

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

yes

SQL-like query language (GQL)

APIs and other access methods

ADO.NET
JDBC
ODBC

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

Java API
RIO

RDF Input/Output
Sail API
SeRQL

Sesame RDF Query Language
Sesame REST HTTP Protocol
SPARQL

HTTP API

Supported programming languages

All languages supporting JDBC/ODBC/ADO.Net

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

Java
PHP
Python

C++
JavaScript (Node.js)
Python
Rust

Java
Kotlin
Scala

Server-side scripts

Stored procedures

Java Stored Procedures

using Google App Engine

yes

Triggers

Callbacks using the Google Apps Engine

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication between multi datacenters

Multi-source replication using Paxos

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

Immediate Consistency

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

Transaction concepts

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

ACID

Isolation support depends on the API used

Atomic execution of operations

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

in-memory storage is supported as well

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, groups and roles based on Google Cloud Identity and Access Management (IAM)

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

Google Cloud vs AWS: Which Cloud Computing Platform is Better?
11 September 2024, Cloudwards

Google Gets Rid of Fees To Transfer Data Out of Cloud Platform
12 January 2024, Spiceworks News and Insights

Best cloud storage of 2024
13 September 2024, TechRadar

Google App Engine
26 April 2024, TechTarget

17 Top Cloud Storage Companies to Know
9 April 2024, Built In

provided by Google News

Share this page