DBMS > Geode vs. Newts vs. Riak TS vs. Snowflake vs. SurrealDB

System Properties Comparison Geode vs. Newts vs. Riak TS vs. Snowflake vs. SurrealDB

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

Time Series DBMS based on Cassandra

Riak TS is a distributed NoSQL database optimized for time series data and based on Riak KV

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

A fully ACID transactional, developer-friendly, multi-model DBMS

Primary database model

Key-value store

Time Series DBMS

Relational DBMS

Document store
Graph 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.07
Rank	#375	Overall
	#41	Time Series DBMS

Score	0.28
Rank	#307	Overall
	#27	Time Series DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	1.02
Rank	#190	Overall
	#33	Document stores
	#18	Graph DBMS

Website

geode.apache.org

opennms.github.io/newts

www.snowflake.com

surrealdb.com

Technical documentation

geode.apache.org/docs

github.com/OpenNMS/newts/wiki

www.tiot.jp/riak-docs/riak/ts/latest

docs.snowflake.net/manuals/index.html

surrealdb.com/docs

Developer

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

OpenNMS Group

Open Source, formerly Basho Technologies

Snowflake Computing Inc.

SurrealDB Ltd

Initial release

2002

2014

2015

2014

2022

Current release

1.1, February 2017

3.0.0, September 2022

v1.5.0, May 2024

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available as Gemfire

Open Source

Apache 2.0

Open Source

commercial

Open Source

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

Erlang

Rust

Server operating systems

All OS with a Java VM

the JDK (8 or later) is also required

Linux
OS X
Windows

Linux
OS X

hosted

Linux
macOS
Windows

Data scheme

schema-free

yes

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

schema-free

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

restricted

SQL

Support of SQL

SQL-like query language (OQL)

yes, limited

yes

SQL-like query language

APIs and other access methods

Java Client API
Memcached protocol
RESTful HTTP API

HTTP REST
Java API

HTTP API
Native Erlang Interface

CLI Client
JDBC
ODBC

GraphQL
RESTful HTTP API
WebSocket

Supported programming languages

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

Java

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

JavaScript (Node.js)
Python

Deno
Go
JavaScript (Node.js)
Rust

Server-side scripts

Stored procedures

user defined functions

Erlang

user defined functions

Triggers

yes

Cache Event Listeners

yes

pre-commit hooks and post-commit hooks

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

based on Cassandra

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

selectable replication factor

based on Cassandra

selectable replication factor

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

links between datasets can be stored

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

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

yes, based on authentication and database rules

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.