DBMS > FileMaker vs. Geode vs. Heroic vs. IBM Db2 warehouse vs. Snowflake

System Properties Comparison FileMaker vs. Geode vs. Heroic vs. IBM Db2 warehouse vs. Snowflake

Editorial information provided by DB-Engines

Name

Description

FileMaker is a cross-platform RDBMS that includes a GUI frontend.

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

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

Cloud-based data warehousing service

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

Primary database model

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

Score	47.91
Rank	#20	Overall
	#14	Relational DBMS

Score	1.86
Rank	#134	Overall
	#24	Key-value stores

Score	0.46
Rank	#265	Overall
	#22	Time Series DBMS

Score	1.37
Rank	#160	Overall
	#74	Relational DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

www.claris.com/filemaker

geode.apache.org

github.com/spotify/heroic

www.ibm.com/products/db2/warehouse

www.snowflake.com

Technical documentation

www.claris.com/resources/documentation

geode.apache.org/docs

spotify.github.io/heroic

docs.snowflake.net/manuals/index.html

Developer

Claris

a subsidiary of Apple

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

Spotify

IBM

Snowflake Computing Inc.

Initial release

1983

2002

2014

Current release

19.4.1, November 2021

1.1, February 2017

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; commercial licenses available as Gemfire

Open Source

Apache 2.0

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

iOS

client part only
Linux
OS X
Windows

All OS with a Java VM

the JDK (8 or later) is also required

hosted

Data scheme

yes

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

A http query request can return the data in XML format

Import/export of XML data possible

yes

Secondary indexes

yes

via Elasticsearch

yes

SQL

Support of SQL

yes

via plugins

SQL-like query language (OQL)

yes

APIs and other access methods

Filemaker WebDirect
JDBC
ODBC

Java Client API
Memcached protocol
RESTful HTTP API

HQL (Heroic Query Language, a JSON-based language)
HTTP API

.NET Client API
JDBC
ODBC
OLE DB

CLI Client
JDBC
ODBC

Supported programming languages

PHP

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

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

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

user defined functions

PL/SQL, SQL PL

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

none

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication, warm standby

since Version 14

Multi-source replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Eventual Consistency
Immediate 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

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

User concepts

Access control

simple rights management via user accounts and connection to external directory services

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.