DBMS > Blueflood vs. Geode vs. PlanetScale vs. Snowflake

System Properties Comparison Blueflood vs. Geode vs. PlanetScale vs. Snowflake

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Scalable TimeSeries DBMS based on Cassandra

Geode is a distributed data container, pooling memory, CPU, network resources, and optionally local disk across multiple processes

Scalable, distributed, serverless MySQL database platform built on top of Vitess

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

Primary database model

Time Series DBMS

Key-value store

Relational DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	0.06
Rank	#352	Overall
	#36	Time Series DBMS

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

Score	1.09
Rank	#178	Overall
	#82	Relational DBMS

Score	133.72
Rank	#7	Overall
	#5	Relational DBMS

Website

Technical documentation

github.com/rax-maas/blueflood/wiki

geode.apache.org/docs

planetscale.com/docs

docs.snowflake.net/manuals/index.html

Developer

Rackspace

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

PlanetScale

Snowflake Computing Inc.

Initial release

2013

2002

2020

2014

Current release

1.1, February 2017

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

Apache Version 2; commercial licenses available as Gemfire

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

Server operating systems

Linux
OS X

All OS with a Java VM

the JDK (8 or later) is also required

Docker
Linux
macOS

hosted

Data scheme

predefined scheme

schema-free

yes

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

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

SQL

Support of SQL

SQL-like query language (OQL)

yes

with proprietary extensions

yes

APIs and other access methods

HTTP REST

Java Client API
Memcached protocol
RESTful HTTP API

ADO.NET
JDBC
MySQL protocol
ODBC

CLI Client
JDBC
ODBC

Supported programming languages

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

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

yes

proprietary syntax

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

based on Cassandra

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

based on Cassandra

Multi-source replication

Multi-source replication
Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Eventual Consistency

Eventual Consistency across shards
Immediate Consistency within a shard

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

yes, on a single node

ACID at shard level

ACID

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

no user groups or roles

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.