DBMS > Geode vs. IBM Db2 warehouse vs. Snowflake vs. Solr vs. SQream DB

System Properties Comparison Geode vs. IBM Db2 warehouse vs. Snowflake vs. Solr vs. SQream DB

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

Cloud-based data warehousing service

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

A widely used distributed, scalable search engine based on Apache Lucene

a GPU-based, columnar RDBMS for big data analytics workloads

Primary database model

Secondary database models

Spatial DBMS

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

Score	1.99
Rank	#133	Overall
	#23	Key-value stores

Score	1.34
Rank	#166	Overall
	#76	Relational DBMS

Score	123.20
Rank	#9	Overall
	#6	Relational DBMS

Score	44.28
Rank	#24	Overall
	#3	Search engines

Score	0.73
Rank	#228	Overall
	#105	Relational DBMS

Website

geode.apache.org

www.ibm.com/products/db2/warehouse

www.snowflake.com

solr.apache.org

sqream.com

Technical documentation

geode.apache.org/docs

docs.snowflake.net/manuals/index.html

solr.apache.org/resources.html

docs.sqream.com

Developer

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

IBM

Snowflake Computing Inc.

Apache Software Foundation

SQream Technologies

Initial release

2002

2014

2006

2017

Current release

1.1, February 2017

9.5.0, February 2024

2022.1.6, December 2022

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available as Gemfire

commercial

Open Source

Apache Version 2

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++, CUDA, Haskell, Java, Scala

Server operating systems

All OS with a Java VM

the JDK (8 or later) is also required

hosted

All OS with a Java VM

runs as a servlet in servlet container (e.g. Tomcat, Jetty is included)

Linux

Data scheme

schema-free

yes

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

yes

Dynamic Fields enables on-the-fly addition of new fields

yes

Typing

predefined data types such as float or date

yes

supports customizable data types and automatic typing

yes, ANSI Standard SQL Types

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.

Import/export of XML data possible

yes

Secondary indexes

yes

All search fields are automatically indexed

SQL

Support of SQL

SQL-like query language (OQL)

yes

Solr Parallel SQL Interface

yes

APIs and other access methods

Java Client API
Memcached protocol
RESTful HTTP API

.NET Client API
JDBC
ODBC
OLE DB

CLI Client
JDBC
ODBC

Java API
RESTful HTTP/JSON API

.Net
JDBC
ODBC

Supported programming languages

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

Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby

JavaScript (Node.js)
Python

.Net
Erlang
Java
JavaScript
any language that supports sockets and either XML or JSON
Perl
PHP
Python
Ruby
Scala

C++
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

PL/SQL, SQL PL

user defined functions

Java plugins

user defined functions in Python

Triggers

yes

Cache Event Listeners

yes

similar concept for controling cloud resources

yes

User configurable commands triggered on index changes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

Sharding

horizontal and vertical partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

spark-solr: github.com/lucidworks/spark-solr and streaming expressions to reduce

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

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

optimistic locking

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

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

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

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.