DBMS > Geode vs. mSQL vs. OrigoDB vs. Snowflake vs. STSdb

System Properties Comparison Geode vs. mSQL vs. OrigoDB vs. Snowflake vs. STSdb

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

mSQL (Mini SQL) is a simple and lightweight RDBMS

A fully ACID in-memory object graph database

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

Key-Value Store with special method for indexing

optimized for high performance using a special indexing method

Primary database model

Key-value store

Relational DBMS

Document store
Object oriented DBMS

Relational DBMS

Key-value store

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

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

Score	1.27
Rank	#167	Overall
	#77	Relational DBMS

Score	0.00
Rank	#383	Overall
	#53	Document stores
	#20	Object oriented DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	0.04
Rank	#360	Overall
	#52	Key-value stores

Website

geode.apache.org

hughestech.com.au/products/msql

origodb.com

www.snowflake.com

github.com/STSSoft/STSdb4

Technical documentation

geode.apache.org/docs

origodb.com/docs

docs.snowflake.net/manuals/index.html

Developer

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

Hughes Technologies

Robert Friberg et al

Snowflake Computing Inc.

STS Soft SC

Initial release

2002

1994

2009

under the name LiveDB

2014

2011

Current release

1.1, February 2017

4.4, October 2021

4.0.8, September 2015

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available as Gemfire

commercial

free licenses can be provided

Open Source

commercial

Open Source

GPLv2, commercial license 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

Server operating systems

All OS with a Java VM

the JDK (8 or later) is also required

AIX
HP-UX
Linux
OS X
Solaris SPARC/x86
Windows

Linux
Windows

hosted

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

User defined using .NET types and collections

yes

primitive types and user defined types (classes)

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.

can be achieved using .NET

yes

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language (OQL)

A subset of ANSI SQL is implemented

no subqueries, aggregate functions, views, foreign keys, triggers

yes

APIs and other access methods

Java Client API
Memcached protocol
RESTful HTTP API

JDBC
ODBC

.NET Client API
HTTP API
LINQ

CLI Client
JDBC
ODBC

.NET Client API

Supported programming languages

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

C
C++
Delphi
Java
Perl
PHP
Tcl

.Net

JavaScript (Node.js)
Python

C#
Java

Server-side scripts

Stored procedures

user defined functions

yes

user defined functions

Triggers

yes

Cache Event Listeners

yes

Domain Events

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

horizontal partitioning

client side managed; servers are not synchronized

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

none

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

none

Immediate Consistency

Foreign keys

Referential integrity

depending on model

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

Write ahead log

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

Role based authorization

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.