DBMS > Geode vs. RDF4J vs. Snowflake vs. Sphinx vs. VelocityDB

System Properties Comparison Geode vs. RDF4J vs. Snowflake vs. Sphinx vs. VelocityDB

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

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

Cloud-based data warehousing service for structured and semi-structured data

Open source search engine for searching in data from different sources, e.g. relational databases

A .NET Object Database that can be embedded/distributed and extended to a graph data model (VelocityGraph)

Primary database model

Graph DBMS
Object oriented DBMS

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

Score	1.86
Rank	#134	Overall
	#24	Key-value stores

Score	0.74
Rank	#222	Overall
	#9	RDF stores

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	5.95
Rank	#55	Overall
	#5	Search engines

Score	0.11
Rank	#354	Overall
	#37	Graph DBMS
	#15	Object oriented DBMS

Website

Technical documentation

geode.apache.org/docs

rdf4j.org/documentation

docs.snowflake.net/manuals/index.html

sphinxsearch.com/docs

velocitydb.com/UserGuide

Developer

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

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

Snowflake Computing Inc.

Sphinx Technologies Inc.

VelocityDB Inc

Initial release

2002

2004

2014

2001

2011

Current release

1.1, February 2017

3.5.1, February 2023

7.x

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available as Gemfire

Open Source

Eclipse Distribution License (EDL), v1.0.

commercial

Open Source

GPL version 2, commercial licence available

commercial

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

C++

Server operating systems

All OS with a Java VM

the JDK (8 or later) is also required

Linux
OS X
Unix
Windows

hosted

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Any that supports .NET

Data scheme

schema-free

yes

RDF Schemas

yes

support of semi-structured data formats (JSON, XML, Avro)

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

full-text index on all search fields

yes

SQL

Support of SQL

SQL-like query language (OQL)

yes

SQL-like query language (SphinxQL)

APIs and other access methods

Java Client API
Memcached protocol
RESTful HTTP API

Java API
RIO

RDF Input/Output
Sail API
SeRQL

Sesame RDF Query Language
Sesame REST HTTP Protocol
SPARQL

CLI Client
JDBC
ODBC

Proprietary protocol

.Net

Supported programming languages

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

Java
PHP
Python

JavaScript (Node.js)
Python

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

.Net

Server-side scripts

Stored procedures

user defined functions

yes

user defined functions

Triggers

yes

Cache Event Listeners

yes

similar concept for controling cloud resources

Callbacks are triggered when data changes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

yes

Sharding

Partitioning is done manually, search queries against distributed index is supported

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

none

yes

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

The original contents of fields are not stored in the Sphinx index.

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

Users with fine-grained authorization concept, user roles and pluggable authentication

Based on Windows Authentication

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.