DBMS > Geode vs. MaxDB vs. Snowflake vs. Sphinx

System Properties Comparison Geode vs. MaxDB vs. Snowflake vs. Sphinx

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

A robust and reliable RDBMS optimized to run all major SAP solutions

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

Primary database model

Key-value store

Relational DBMS

Search engine

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

Score	1.51
Rank	#147	Overall
	#25	Key-value stores

Score	2.15
Rank	#115	Overall
	#55	Relational DBMS

Score	133.72
Rank	#7	Overall
	#5	Relational DBMS

Score	5.97
Rank	#56	Overall
	#5	Search engines

Website

Technical documentation

geode.apache.org/docs

maxdb.sap.com/documentation

docs.snowflake.net/manuals/index.html

sphinxsearch.com/docs

Developer

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

SAP, acquired from Software AG (Adabas-D) in 1997

Snowflake Computing Inc.

Sphinx Technologies Inc.

Initial release

2002

1984

2014

2001

Current release

1.1, February 2017

7.9.10.12, February 2024

3.5.1, February 2023

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available as Gemfire

commercial

Limited community edition free

commercial

Open Source

GPL version 2, commercial licence 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

Java

C++

Server operating systems

All OS with a Java VM

the JDK (8 or later) is also required

AIX
HP-UX
Linux
Solaris
Windows

hosted

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Data scheme

schema-free

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

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

ADO.NET
JDBC
ODBC
WebDAV

CLI Client
JDBC
ODBC

Proprietary protocol

Supported programming languages

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

.Net
C#
Java
Perl
PHP
Python

JavaScript (Node.js)
Python

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

Server-side scripts

Stored procedures

user defined functions

yes

user defined functions

Triggers

yes

Cache Event Listeners

yes

similar concept for controling cloud resources

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

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

Source-replica replication

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

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

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

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

Users with fine-grained authorization concept, user roles and pluggable 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.