DBMS > Geode vs. Microsoft SQL Server vs. RDF4J vs. WakandaDB

System Properties Comparison Geode vs. Microsoft SQL Server vs. RDF4J vs. WakandaDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Geode is a distributed data container, pooling memory, CPU, network resources, and optionally local disk across multiple processes

Microsofts flagship relational DBMS

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

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

Document store
Graph DBMS
Spatial DBMS

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

Score	1.92
Rank	#131	Overall
	#23	Key-value stores

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	0.69
Rank	#230	Overall
	#9	RDF stores

Score	0.03
Rank	#364	Overall
	#17	Object oriented DBMS

Website

geode.apache.org

www.microsoft.com/en-us/sql-server

rdf4j.org

wakanda.github.io

Technical documentation

geode.apache.org/docs

learn.microsoft.com/en-US/sql/sql-server

rdf4j.org/documentation

wakanda.github.io/doc

Developer

Originally developed by Gemstone. They outsourced the project to Apache in 2015 but still deliver a commercial version as Gemfire.

Microsoft

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

Wakanda SAS

Initial release

2002

1989

2004

2012

Current release

1.1, February 2017

SQL Server 2022, November 2022

2.7.0 (April 29, 2019), April 2019

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available as Gemfire

commercial

restricted free version is available

Open Source

Eclipse Distribution License (EDL), v1.0.

Open Source

AGPLv3, extended commercial license available

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

Java

C++

Java

C++, JavaScript

Server operating systems

All OS with a Java VM

the JDK (8 or later) is also required

Linux
Windows

Linux
OS X
Unix
Windows

Linux
OS X
Windows

Data scheme

schema-free

yes

RDF Schemas

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

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language (OQL)

yes

APIs and other access methods

Java Client API
Memcached protocol
RESTful HTTP API

ADO.NET
JDBC
ODBC
OLE DB
Tabular Data Stream (TDS)

Java API
RIO

RDF Input/Output
Sail API
SeRQL

Sesame RDF Query Language
Sesame REST HTTP Protocol
SPARQL

RESTful HTTP API

Supported programming languages

.Net
All JVM based languages
C++
Groovy
Java
Scala

C#
C++
Delphi
Go
Java
JavaScript (Node.js)
PHP
Python
R
Ruby
Visual Basic

Java
PHP
Python

JavaScript

Server-side scripts

Stored procedures

user defined functions

Transact SQL, .NET languages, R, Python and (with SQL Server 2019) Java

yes

Triggers

yes

Cache Event Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

tables can be distributed across several files (horizontal partitioning); sharding through federation

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes, but depending on the SQL-Server Edition

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes, on a single node

ACID

Isolation support depends on the API used

ACID

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

Access rights per client and object definable

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.