DBMS > EsgynDB vs. Google Cloud Datastore vs. Machbase Neo vs. RDF4J vs. Sadas Engine

System Properties Comparison EsgynDB vs. Google Cloud Datastore vs. Machbase Neo vs. RDF4J vs. Sadas Engine

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

TimeSeries DBMS for AIoT and BigData

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

SADAS Engine is a columnar DBMS specifically designed for high performance in data warehouse environments

Primary database model

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

Score	0.25
Rank	#312	Overall
	#138	Relational DBMS

Score	4.36
Rank	#72	Overall
	#12	Document stores

Score	0.17
Rank	#337	Overall
	#30	Time Series DBMS

Score	0.74
Rank	#222	Overall
	#9	RDF stores

Score	0.07
Rank	#373	Overall
	#157	Relational DBMS

Website

www.esgyn.cn

cloud.google.com/datastore

machbase.com

rdf4j.org

www.sadasengine.com

Technical documentation

cloud.google.com/datastore/docs

machbase.com/dbms

rdf4j.org/documentation

www.sadasengine.com/en/sadas-engine-download-free-trial-and-documentation/#documentation

Developer

Esgyn

Google

Machbase

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

SADAS s.r.l.

Initial release

2015

2008

2013

2004

2006

Current release

V8.0, August 2023

8.0

License

Commercial or Open Source

commercial

free test version available

Open Source

Eclipse Distribution License (EDL), v1.0.

commercial

free trial version 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

C++, Java

Java

C++

Server operating systems

Linux

hosted

Linux
macOS
Windows

Linux
OS X
Unix
Windows

AIX
Linux
Windows

Data scheme

yes

schema-free

yes

RDF Schemas

yes

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)

SQL-like query language

yes

APIs and other access methods

ADO.NET
JDBC
ODBC

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

gRPC
HTTP REST
JDBC
MQTT (Message Queue Telemetry Transport)
ODBC

Java API
RIO

RDF Input/Output
Sail API
SeRQL

Sesame RDF Query Language
Sesame REST HTTP Protocol
SPARQL

JDBC
ODBC
Proprietary protocol

Supported programming languages

All languages supporting JDBC/ODBC/ADO.Net

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

C
C#
C++
Go
Java
JavaScript
PHP

via ODBC
Python
R

via ODBC
Scala

Java
PHP
Python

.Net
C
C#
C++
Groovy
Java
PHP
Python

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

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication between multi datacenters

Multi-source replication using Paxos

selectable replication factor

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

yes

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

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

volatile and lookup table

yes

managed by 'Learn by Usage'

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)

simple password-based access control

Access rights for users, groups and roles 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

Recent citations in the news

Best cloud storage of 2024
4 June 2024, TechRadar

Google Cloud Stops Exit Fees
12 January 2024, Spiceworks News and Insights

BigID Data Intelligence Platform Now Available on Google Cloud Marketplace
6 November 2023, PR Newswire

Google says it'll stop charging fees to transfer data out of Google Cloud
11 January 2024, TechCrunch

Inside Google’s strategic move to eliminate customer cloud data transfer fees
12 January 2024, Network World

provided by Google News

GraphDB Goes Open Source
27 January 2020, iProgrammer

Ontotext's GraphDB 8.10 Makes Knowledge Graph Experience Faster and Richer
13 June 2019, Markets Insider

provided by Google News

Share this page